Both rows have been citing closed P0s as open for 25 rounds. The
round-17 fixes (harsh-critic findings #3, #4, #7, #8 per
docs/BACKLOG.md:286-299) closed the blocking correctness bugs:

- Residuated.fs: top-2 cache replaced with SortedSet + weight
  dict; every op O(log k), no linear-scan fallback. The round-12
  "O(1)" claim was false under adversarial retract-top workloads;
  the corrected "O(log k) genuinely" claim has been stable 25
  rounds. See Residuated.fs:39-48 for the fix-in-code narrative.

- FastCdc.fs: persistent scanCursor + hash (each byte Gear-hashed
  exactly once across lifetime) closed the O(n^2) buffer scan;
  Buffer.BlockCopy replaced per-byte ResizeArray.Add. See
  FastCdc.fs:68-76 for the fix-in-code narrative. Paper
  throughput target 1-3 GB/s/core holds.

Rows now match the Bloom Round-40 graduation pattern (measured-
evidence cite, implementation line reference, test coverage
pointer). 25-round stability window beats the aspirational
waiting-list — graduation on evidence, not aspiration.

BP-10 clean; 0 invisible-unicode on edited file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ion annotation

Aarav (skill-tune-up) round-42 cadence discharge. Round-41
top-5 carries over; self-rank escalates to P1 #4 after
commit baa423e retuned skill-tune-up/SKILL.md 303 -> 436
lines (1.45x BP-03 cap). claims-tester / complexity-reviewer
hand-off carry-over from round 18 drops off top-5 (resolved
via commit e8ed0db + router-coherence-v2 ADR).

Files:
- memory/persona/aarav/NOTEBOOK.md: round-42 observation
  + top-5 revision (skill-tune-up self escalated) + archived
  round-41 top-5 + calibration preamble flagging the ranking
  as static-signals-only with a harness run scheduled for
  round 43 (per Aaron's round-42 correction that "worst
  performance" claims must drive the Anthropic skill-creator
  eval harness rather than guessing by inspection).
- memory/persona/best-practices-scratch.md: F7-F9 live-search
  entries from Aarav's round-42 pass (Anthropic skill-
  authoring Apr 2026, OWASP Top 10 Agentic 2026, skill
  wrapper thick-vs-thin 2026). Zero contradictions with
  stable BP-NN; zero promotion candidates this round.
- docs/BACKLOG.md: P2 entry for resolving the skill-tune-up
  BP-03 self-breach. Binary remedy: (a) Kenji-ADR declaring
  non-skill-wrapper exception to BP-03 or (b) extract
  eval-loop protocol body to docs/references/ so the skill
  file shrinks under 300 lines. Composes with the
  skill-eval-tools calibration memory saved this round.

Aarav's round-42 self-flag (BACKLOG P2, filed commit 45369ae)
resolved via the mechanical-edit path of the gate table.
.claude/skills/skill-tune-up/SKILL.md shrinks 436 -> 282
lines (54 under the 300-line BP-03 cap) by extracting two
reference blocks verbatim:

- §"The eval-loop hand-off protocol" (~130 lines) — the
  gate table, per-round protocol, stopping criteria, ledger
  row, and deliberately-not-reimplemented list.
- Notebook format + ranking-round output format templates
  (~55 lines).

Extracted content lives at docs/references/skill-tune-up-
eval-loop.md alongside the existing Anthropic skills guide
references. SKILL.md retains a short pointer block.

No change to triggering behaviour, output shape, or
instruction-following — the ranker reading the pointer-plus-
reference produces the same ranking output as the ranker
reading the pre-extract inline version. This is why the
manual-edit path (gate table "mechanical rename | content
extract preserving protocol verbatim") applies instead of
the full eval-loop path.

Files:
- .claude/skills/skill-tune-up/SKILL.md: 436 -> 282 lines.
- docs/references/skill-tune-up-eval-loop.md: NEW. Hosts
  the extracted protocol + templates + rationale.
- docs/skill-edit-justification-log.md: NEW. First row
  documents this extraction per
  memory/feedback_skill_edits_justification_log_and_tune_up_cadence.md
  Rule 1. Template for future mechanical-edit rows
  included.
- memory/persona/aarav/NOTEBOOK.md: self-flag #4 marked
  RESOLVED; drops off top-5 next invocation.

Does NOT rebut the round-42 harness-calibration memory
(feedback_skill_tune_up_uses_eval_harness_not_static_line_
count.md). That rule applies to "worst-performing" ranking
claims; this edit is a fix-my-own-size hygiene pass on the
mechanical-edit path, which is explicitly separate in the
gate table.

)

* Round 41: OpenSpec coverage audit + backfill-program ADR

Answers Aaron 2026-04-20 delete-all-code-recovery question:
4 capabilities / 783 lines of spec.md vs 66 top-level F#
modules / 10,839 lines under src/Core/ — ~6% coverage today.

docs/research/openspec-coverage-audit-2026-04-21.md
- Inventory of 66 modules with line counts + capability
  mapping for the 4 existing capabilities
- Uncovered modules sorted by delete-recovery blast radius:
  Band 1 MUST BACKFILL (8 modules / 1,629 lines — ZSet,
  Circuit, NestedCircuit, Spine family, BloomFilter as
  Adopt-row compatibility-coupling exception), Band 2 HIGH
  (12 / 2,008), Band 3 MEDIUM (45 / 6,585), Band 4
  deliberately uncovered (AssemblyInfo only)
- First 6-round cadence: operator-algebra extension (41),
  lsm-spine-family (42), circuit-recursion (43),
  sketches-probabilistic (44), content-integrity (45),
  crdt-family (46)
- Success signal = Viktor spec-zealot adversarial audit:
  "could I rebuild this module from this spec alone?"

docs/DECISIONS/2026-04-21-openspec-backfill-program.md
- Adopts one-capability-per-round baseline with paper-grade
  half-credit rule (no more than 1 paper-grade round per 3)
- Band 1 priority until complete; Adopt-row escalation for
  BloomFilter (TECH-RADAR Adopt without spec contract is a
  backwards-compatibility hazard)
- Round-close ledger gains an `OpenSpec cadence` line
- Alternatives considered: big-bang backfill (rejected —
  ontology-landing cadence + reviewer bandwidth), per-module
  capabilities (rejected — loses cross-module invariants),
  organic prioritisation (rejected — 40 rounds of drift
  evidence)

docs/BACKLOG.md
- Collapses the 29-line P0 scope into a 15-line pointer at
  the inventory + ADR now that parts (a)-(e) of the program
  setup have landed. Remaining work = per-round capability
  backfill per ADR schedule.

Build: dotnet build -c Release clean; BP-10 ASCII-clean on
all 3 modified files; markdownlint-cli2 clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: operator-algebra spec extension (cadence ship)

First ship under the OpenSpec backfill program adopted
2026-04-21. Extends openspec/specs/operator-algebra/spec.md
(184 -> 324 lines) with five new requirements covering
structural and lifecycle gaps that the existing mathematical-
law coverage left implicit:

1. Operator lifecycle — construction / step / after-step /
   reset phases with side-effect-freedom on construction and
   epoch-replay semantics on reset
2. Strict operators break feedback cycles — formalises that
   z^-1-on-feedback is a scheduling prerequisite and that
   cycle-without-strict is a construction error, not a
   silent heuristic
3. Clock scopes and tick monotonicity — nested-scope-to-
   fixpoint rule + sibling-scope independence
4. Incremental-wrapper preserves the chain rule —
   Incrementalize(Q) observably equivalent to D . Q . I,
   with linear/bilinear substitution permitted as an
   optimisation
5. Representation invariants of the reference Z-set —
   O(n+m) group ops + zero-alloc iteration as the reference
   contract; hash-table recoveries permitted at documented
   perf trade-off

Disaster-recovery effect: a contributor with only this spec
(plus the durability-modes + retraction-safe-recursion specs)
can now rebuild Circuit.fs Op base + Incremental.fs wrapper +
ZSet.fs representation invariants from the spec text alone.

Owner: Architect (Kenji). Adversarial audit by Viktor
(spec-zealot) is the ADR-declared ship-gate and will run
post-land.

Build: not rebuilt (no F# source changed); markdownlint
clean; BP-10 ASCII clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close Viktor P0 findings on operator-algebra spec

Viktor's adversarial audit of the Round 41 cadence ship (commit
e51ec1b) surfaced four P0 findings against the disaster-recovery
bar. This commit closes all four:

- **P0-1 (namespace drift).** `profiles/fsharp.md` asserted
  `Dbsp.Core` throughout, but `src/Core/**` uses `Zeta.Core`. A
  spec-only recovery would have shipped the wrong namespace to
  every downstream consumer. Replaced via one `replace_all` Edit.

- **P0-2 (phantom Reset method).** The lifecycle requirement
  claimed a `reset` phase that does not exist on `Op`. Replaced
  the "reset replays the epoch" scenario with a
  determinism-under-structural-equivalence property: two
  freshly-constructed circuits of the same topology, stepped
  with the same input sequence, MUST produce identical outputs
  at every tick. Reconstruction is the supported route to a
  replayed epoch.

- **P0-3 (after-step scope).** The lifecycle requirement said
  after-step runs "after every operator in the scope has
  completed its step." `Circuit.fs:205-208` iterates the
  `strictN` array only — after-step is selective to strict
  operators. Fixed wording and added a "after-step is selective
  to strict operators" scenario that pins the invariant.

- **P0-4 (lifecycle phase undercount).** The requirement named
  four phases (construction / step / after-step / reset) but
  the code has five (construction / step / after-step /
  clock-start / clock-end). Restructured to three per-tick
  phases plus two scope-boundary phases, and extended the
  "clock scopes and tick monotonicity" requirement with the
  scope-boundary lifecycle contract (clock-start before tick 0
  of a scope, clock-end after fixpoint or iteration cap).

Build green (0 warnings / 0 errors). BP-10 lint clean. The
capability now reflects the code's observable shape rather than
an idealised cleaner cousin; a delete-recovery from this spec
produces Zeta.Core with strict-operator after-step selectivity
and nested-scope clock-boundary phases.

Viktor's 10 P1 findings (async lifecycle, memory-ordering fence,
register-lock semantics, IncrementalDistinct surface, ZSet sort
invariant, Checked arithmetic, bilinear-size overflow,
convergence-vs-cap) are deferred to Round 42 — filed as a
BACKLOG sweep in follow-up work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: file Viktor P1 findings as Round 42 BACKLOG absorb

Companion to 92d7db2 (closing Viktor's four P0 findings). The
ten P1-tier surface gaps Viktor identified do not block the
disaster-recovery bar at capability-close but leave the
operator-algebra spec incomplete relative to what a delete-
recovery produces. Filed as a dedicated P0 sub-item so they
travel with the OpenSpec backfill program rather than getting
lost: async lifecycle, memory-ordering fence, register-lock
semantics, IncrementalDistinct surface, ZSet sort invariant,
Checked arithmetic, bilinear-size overflow, convergence-vs-cap,
Op.Fixedpoint predicate, DelayOp reconstruction-first-tick.

Also annotated the parent OpenSpec coverage entry with Round 41
sweep status (e51ec1b + 92d7db2, P0s closed, P1s deferred) so
the backlog accurately reflects where the program stands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: ROUND-HISTORY entry — OpenSpec backfill founding + first cadence ship

Four-arc entry at the top of the file per newest-first policy:

- Arc 1 (d435126): OpenSpec coverage audit + backfill-program
  ADR. Measured 6% coverage; declared one-capability-per-round
  baseline with paper-grade half-credit and Adopt-row priority
  escalation; banded 66 F# modules by delete-recovery blast
  radius.
- Arc 2 (e51ec1b): operator-algebra extension as Round-41
  cadence ship. Five new requirements covering lifecycle,
  strict-operator scheduling, clock scopes, Incrementalize
  wrapper, ZSet representation invariants.
- Arc 3 (92d7db2): Viktor P0 close. Four drift-from-code
  defects fixed — namespace (Dbsp.Core → Zeta.Core), phantom
  Reset, after-step scope (strict-only), lifecycle phase
  undercount (3 per-tick + 2 scope-boundary).
- Arc 4 (56f34b5): Viktor P1s filed as Round-42 absorb under
  the parent backfill P0, creating mechanical coupling between
  each capability ship and the following round's P1 sweep.

Round-41 observations for Round 42 + prospective BP-WINDOW
ledger table rendering the four commits against the consent /
retractability / no-permanent-harm axes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: memory-folder role-restructure — design plan + BACKLOG pointer

Aaron 2026-04-19 asked for memory/role/persona/ so roles become
first-class in the directory structure. Surface is wider than
it first looks — 114 files / ~260 hand-written references to
memory/persona/ paths (plus ~440 auto-regenerated references
in tools/alignment/out/ that refresh on next citations.sh run).
A bad role axis is hard to reverse; this design doc proposes
the axis and holds execution for Aaron's sign-off rather than
just-doing-it under Auto Mode.

Design plan lands at:
  docs/research/memory-role-restructure-plan-2026-04-21.md

Contents: 13-directory role axis (architect, security,
verification, review, experience, api, performance, devops,
algebra, skill-ops, maintainer, homage, alignment);
persona-to-role crosswalk for every current directory;
5-phase execution plan (pre-flight greps → git mv → sed
passes → 5-check verification → pointer-source updates);
special-case handling for aaron (human maintainer),
rodney (homage-named AI persona on the reducer skill),
sova (emerging alignment-observability role); rollback
plan (one atomic commit, git revert); four open questions
for Aaron on axis judgement-calls.

BACKLOG entry updated to reflect design-landed state with
execution-slot recommendation for Round 42 opener after the
Round 41 PR merges (keeps wide-surface reviews from
overlapping).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: actualise Rounds 37-40 BP-WINDOW ledgers (PR #30 merged)

Rounds 37-40 shipped via PR #30 (merge commit 1e30f8c, 2026-04-20).
Ledger headers updated from "(prospective)" to "(merged via PR #30,
1e30f8c)" — the BP-WINDOW scores are now settled, not forecasts.

Round 41 ledger remains "(prospective)" — round-41 branch has not
merged to main yet.

Prose uses of "prospective" on lines 437, 447, 553, etc. are
historical-narrative commentary on authoring-time methodology and
stay as-is.

* Round 41: Soraya tool-coverage audit on RecursiveSigned skeleton

Round 39 observation flagged src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla as held pending
formal-verification-expert tool-coverage review. Round 41 closes
that gate.

Soraya's notebook entry lands:

- Per-property tool table S1-S4 + refinement cross-check. TLC
  primary for S1/S2/S3/S3'/SupportMonotone; FsCheck for S4.
- S2 flagged as the one P0 on the spec (silent fixpoint drift
  unrecoverable); BP-16 requires Z3 QF_LIA cross-check.
- Refinement mapping: FsCheck cross-trace (signed vs counting at
  SeedWeight=1) wins over TLA+ refinement proof or Lean lemma —
  anti-TLA+-hammer, implementation-level where the bug bites.
- Readiness gate: TLA+ spec is ready to model-check; no pre-TLC
  pass needed. Optional round-42 follow-up: add
  PROPERTY EventuallyDone to .cfg for liveness.
- Graduation verdict: CONDITIONAL PASS. Four tool-coverage
  prereqs named in priority order; F# landing gated on them.

Files read (no edits): RecursiveSigned.fs, RecursiveSignedSemiNaive.tla
/cfg, RecursiveCountingLFP.tla, retraction-safe-semi-naive.md.

* Round 41: capture Soraya's 4 tool-coverage prereqs on RecursiveSigned

Soraya's round-41 audit of src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla landed as a CONDITIONAL
PASS for Round-42 graduation. This commit lifts the four named
prereqs out of her notebook into BACKLOG sub-items under the
parent "Retraction-safe semi-naive LFP" entry, so the round-42
opener picks them up as checkbox work rather than having to re-read
the notebook.

Prereqs in priority order:
- Prereq 1 — TLC CI wire-up (RecursiveSignedSemiNaive.cfg)
- Prereq 2 — Z3 QF_LIA lemma for S2 FixpointAtTerm (BP-16 cross-check
  on the one P0; TLC alone insufficient for silent-fixpoint-drift risk)
- Prereq 3 — FsCheck property for S4 sign-distribution (anti-
  TLA+-hammer; two-trace quantification is NOT a TLA+ property)
- Prereq 4 — FsCheck cross-trace refinement (signed vs counting
  at SeedWeight = 1); cites BP-16

Round-42 graduation gate also captured: prereqs 1-4 CI-green + F#
implementation with P1/P2/P3 enforced at caller.

* Round 41: extend ROUND-HISTORY with arcs 5-7 (post-narrative commits)

The initial Round 41 ROUND-HISTORY entry (6e6e211) covered arcs
1-4 (coverage audit, operator-algebra cadence ship, Viktor P0
close, Viktor P1 file). Three more commits landed after:

Arc 5 — ROUND-HISTORY narrative + memory-restructure design
(6e6e211, 36797ba). The memory-folder rename was downgraded to
"design plan + sign-off first" under Auto Mode's
do-not-take-overly-destructive-actions clause (700-occurrence
cross-reference surface).

Arc 6 — BP-WINDOW ledger actualisation for Rounds 37-40
(85fb352). Provenance (PR #30 / 1e30f8c) attached to each
"(prospective)" header.

Arc 7 — Round-35 holdover close (e461d9c, 15e9654). Soraya
tool-coverage audit landed CONDITIONAL PASS for Round-42
graduation; four prereqs captured as BACKLOG sub-items with
BP-16 citation on the S2 Z3 cross-check.

Also: one new observation line in the Round-42 handoff section
noting the holdover-closed-same-round-as-cadence-item pattern.
BP-WINDOW ledger gains three rows.

* Round 41: Aarav skill-tune-up ranking (catch-up from round-18 stale)

CLAUDE.md 5-10 round cadence rule was 23 rounds overdue. Round 41
is the catch-up slot. Live-search + full ranking + prune pass all
landed in a single invocation.

Live-search (4 queries, 2026-Q1/Q2 best-practices targets):
- 6 findings logged to best-practices-scratch.md: Gotchas-section
  rise, pushy-descriptions pattern, Claude-A-authors / Claude-B-
  tests, router-layer command-integrity injection class, Agent
  Stability Index 12-dim drift metric, OWASP Intent Capsule
  pattern.
- Zero contradictions with stable BP-NN rules.
- Zero promotions flagged to Architect this round; all six are
  "watch" or route-elsewhere.

Top-5 skills flagged for tune-up:
1. performance-analysis-expert (642 lines, 2.1x BP-03 cap) — SPLIT — M
2. reducer (570 lines) — SPLIT or TUNE (prune) — M
3. consent-primitives-expert (507 lines) — SPLIT honouring BP-23
   theory/applied axis — M
4. claims-tester / complexity-reviewer router-coherence drift —
   HAND-OFF-CONTRACT — S (round-18 carry-over)
5. skill-tune-up (self) — 303 lines, 3 over BP-03 — TUNE (prune
   authoritative-sources duplicated with AGENT-BEST-PRACTICES.md)
   — S. Self-flagged first per BP-06.

Notebook state:
- Stale round-18 top-5 archived in Pruning log (first catch-up prune).
- 912 words, well under 3000-word BP-07 cap.
- ASCII-only, BP-10 clean.

Nine more bloat-row skills named as notable mentions queue behind
the top-3 bloat cases.

* Round 41: ADR — claims-tester/complexity-reviewer hand-off contract

Close Aarav's round-18 HAND-OFF-CONTRACT finding (carried 23 rounds
after ranker went offline by cadence). Two-stage pipeline: analytic
bound first (complexity-reviewer), empirical measurement second
(claims-tester). Names the reverse trigger (benchmark surprise flows
the other direction) and the decision table for who fires when.
Follow-up SKILL.md edits route via skill-creator per GOVERNANCE §4.

* Round 41: extend ROUND-HISTORY with Arc 8 (router-coherence ADR)

Arc 8 covers the claims-tester/complexity-reviewer hand-off ADR
(47d92d8) closing Aarav's 23-round-stale round-18 HAND-OFF-CONTRACT
finding. New observation on cadence-outage-recovery as a design axis:
sweep infrastructure is subject to the same bitrot it detects on other
surfaces. BP-WINDOW ledger gains two rows (085c0e3 Aarav catch-up,
47d92d8 router-coherence ADR).

* Round 41: correct Prereq 1 sizing — no TLC CI job exists

Close-out audit surfaced that .github/workflows/gate.yml only CACHES
the tla2tools.jar artefact; nothing runs it. RecursiveCountingLFP.tla
has shipped since round 19 compile-checkable-only — 22 rounds with no
run-gate against its invariants. Soraya's Prereq 1 re-sized S→M with
expanded scope covering both specs. Finding recorded as new round-41
observation: verifier-present does not imply verifier-actually-runs.

* Round 41: BP-WINDOW ledger — 459b218 + d76a09b rows

Keeps the Round 41 BP-WINDOW ledger commit-aligned rather than
arc-aligned. 459b218 is the Arc-8 narrative itself; d76a09b is the
Prereq-1 S→M correction. Both retractable as single reverts.

* Round 41: file formal-analysis-gap-finder round-42 run — verifier-runs lens

Codifies the round-41 Prereq-1 audit finding as a tracked
research entry, distinct from its ROUND-HISTORY narrative
presence. The finding — a verifier's installation artefacts
do not imply the verifier is exercised by any CI job — is
exactly the class formal-analysis-gap-finder exists to
surface. Concrete motivating case: RecursiveCountingLFP.tla
compile-checkable-only for 22 rounds. Round-42 scope covers
the bidirectional audit (specs without gates + gates without
specs). Handoff to Soraya per the skill's standing contract;
does not write the spec or CI job (DevOps + Soraya work).
Schedules after Prereq 1 lands so the audit sees corrected
state.

* Round 41: BP-WINDOW ledger — 2042a85 row

Per the established stopping rule (meta-ledger commits do not
get self-referential rows; their round-close coverage is the
PR merge), this commit adds only the 2042a85 row and does not
add a row for itself.

* Round 41: CONFLICT-RESOLUTION — Hiroshi ↔ Daisy hand-off row

Closes ADR 47d92d8's third follow-up action item. Single-row
addition to Active tensions citing the router-coherence ADR as
the standing resolution. Doc-only edit (not a SKILL.md touch,
so GOVERNANCE §4 does not gate this). The other two ADR
follow-ups (claims-tester + complexity-reviewer SKILL.md
updates) remain deferred to round 42 via skill-creator
workflow.

* Round 41: BP-WINDOW ledger — fcfa3d9 row

Per-commit ledger discipline for the CONFLICT-RESOLUTION
Hiroshi ↔ Daisy row. Meta-ledger-only commit so no
self-referential row for this commit itself (established
stopping rule).

* Round 41: file harsh-critic findings on ADR 47d92d8 as round-42 supersedure backlog

Router-coherence ADR 47d92d8 (Hiroshi analytic ↔ Daisy empirical
two-stage pipeline) landed without the adversarial-review gate.
Post-landing harsh-critic (Kira) pass surfaced 3 P0 + 5 P1 + 2 P2
substantive findings, including (P0-1) unscoped grandfather
clause, (P0-2) table-vs-prose contradiction on reverse trigger,
(P0-3) Stage-1 "analytically wrong" clause blocking the evidence
loop for escalation, (P1-7) no escalation timebox reproducing the
23-round-stale failure mode the ADR diagnosed, (P1-8) two advisory
skills not composing to a mandatory pipeline without a binding
dispatcher, (P2-9) example-bug on BCL Dictionary.Remove amortised
complexity, and more.

File as round-42 supersedure rather than inline-edit because
docs/CONFLICT-RESOLUTION.md already cites 47d92d8 as Standing
Resolution — supersedure preserves the citation chain via
GOVERNANCE §2 edit-in-place with a "Superseded by …" header on
v1. New ADR target: docs/DECISIONS/2026-04-??-router-coherence-
v2.md. Supersedure work blocks the claims-tester +
complexity-reviewer SKILL.md updates ADR 47d92d8 follow-up work
depends on — those edits should target v2, not v1.

Owner: Architect drafts; Kira audits closure; Aarav confirms
router-coherence drift stays closed. Effort: M. Schedule: Round
42 slot after Soraya Prereq 1 (TLC wire-up) lands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 779d7ef row

Ledger row for harsh-critic findings filing commit. Primary work
(BACKLOG addition tracking a round-42 supersedure with 10 named
findings), not meta-ledger — earns a row under the BP-WINDOW
per-commit discipline. Consent = adversarial findings tracked
honestly; Retractability = supersedure preserves citation chain
vs inline-edit; No-permanent-harm = single BACKLOG edit, no ADR
body touched, no SKILL.md touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 9 narrative — self-correction sweep

ROUND-HISTORY Arc 1-8 narrated primary commits up through the
router-coherence ADR (47d92d8). Four primary commits landed
after Arc 8 — Prereq 1 sizing correction (d76a09b), recurring-
audit lens BACKLOG entry (2042a85), CONFLICT-RESOLUTION Hiroshi
↔ Daisy row (fcfa3d9), and harsh-critic findings filed as
round-42 supersedure (779d7ef) — visible only in the BP-WINDOW
ledger table, not in narrative form.

Arc 9 ties them into one coherent sequence: the round's
self-correction ran unusually deep. Arc 8 corrects Aarav's
round-18 finding via ADR; Arc 9 catches the corrector itself
under-reviewed via Kira's adversarial pass. Both self-
corrections land before round-close. Narrative-ledger
alignment is the BP-WINDOW discipline's first assertion —
restoring it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 160fcfa row

Ledger row for Arc 9 narrative commit. Narrative extensions
count as primary work under BP-WINDOW precedent (per 459b218
and 6e6e211 examples) and earn a ledger row. Consent = drift
closed honestly; Retractability = single revertable doc edit;
No-permanent-harm = isolated insertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v2 ADR — router-coherence supersedure closes 10 Kira findings in-round

Drafts v2 of the router-coherence ADR (docs/DECISIONS/2026-04-21-router-coherence-v2.md) that supersedes v1 (47d92d8) in the same round, closing all 10 Kira harsh-critic findings (3 P0 + 5 P1 + 2 P2) via named textual closures C-P0-1 through C-P2-10.

Key closures:
- C-P0-1: grandfather clause bounded with Kenji-owned inventory + one-per-round discharge
- C-P0-2: reverse trigger unconditional (table now matches prose)
- C-P0-3: escalation-evidence exception permits Stage 2 under conference protocol with explicit labelling
- C-P1-5: Stage-1 trigger widened to match claims-tester SKILL.md contract
- C-P1-7: escalation timebox (round +2 auto-promote to BACKLOG P1) prevents 23-round-stale reproduction
- C-P1-8: Kenji named as binding dispatcher — advisory + advisory + binding-dispatcher composes to mandatory pipeline
- C-P2-9: Dictionary.Remove example replaced with ArrayPool<T>.Rent (legitimate BCL-contract edge)

v1 kept in place per GOVERNANCE §2 with Superseded-by header appended in a follow-up commit so the CONFLICT-RESOLUTION Active-tensions citation chain remains resolvable.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v1 ADR — append Superseded-by header per GOVERNANCE §2

Appends Superseded-by header to router-coherence v1 ADR (47d92d8) pointing at v2 (09f0889), per GOVERNANCE §2 (docs read as current state; superseded ADRs keep v1 in place with redirect header so citation chains remain resolvable).

Also corrects v1 Status from "Proposed — awaits sign-off" to "Accepted (pre-adversarial-review; superseded by v2 same-round after Kira pass)" per Closure C-P1-4 in v2 — Status was already cited as Standing Resolution in docs/CONFLICT-RESOLUTION.md Active-tensions, so Proposed was factually wrong.

The v1 body text is not edited — supersedure preserves the historical record; v2 carries the closures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 10 narrative + BP-WINDOW rows for v2 supersedure

Adds Arc 10 narrative covering 09f0889 (v2 ADR) and 4efe545 (v1 Superseded-by header) as one coherent in-round supersedure story, after Arc 9's "self-correction sweep" and before Round 41 observations. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring a known-imperfect artefact.

Adds two BP-WINDOW ledger rows (09f0889, 4efe545) to the round-41 ledger block per the per-commit accounting discipline.

Supersedure arc count now covers the full round-41 close: 10 arcs / 25 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close BACKLOG supersedure entry — discharged in-round by v2

Flips BACKLOG router-coherence supersedure entry from [ ] to [x] ✅ with "shipped round 41 in-round" annotation pointing at v2 ADR (09f0889) + v1 Superseded-by header (4efe545). All 10 Kira findings closed via named textual closures C-P0-1 through C-P2-10.

Original finding narrative preserved below the closure line per the shipped-item convention used elsewhere in the file (audit trail).

Follow-up SKILL.md edits to claims-tester + complexity-reviewer via skill-creator remain round-42 scope, now targeting v2 as intended.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW row for BACKLOG-close commit 4537365

Adds BP-WINDOW ledger row for 4537365 (BACKLOG supersedure entry discharged in-round) to match the Arc 9 precedent where 779d7ef (BACKLOG entry addition) received a row. Symmetry: add and close get equal ledger treatment.

Meta-ledger stopping rule still holds — this commit itself (which only adds a ledger row) does not get a self-referential row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: grandfather O(·) claims inventory — honours v2 C-P0-1 within-round

Produces the one-time grandfather-claims inventory named in router-coherence v2 ADR §Closure C-P0-1 within the round v2 lands, per ADR's own within-round commitment.

Inventory: 35 live claims at ADR-landing time (29 F# /// docstrings in src/Core/ + src/Bayesian/, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Zero hits in root README, memory/persona/*/NOTEBOOK.md, docs/papers/** (directory does not exist yet).

Distinguishes live claims (shipping as asserted bounds) from historical evidence (BACKLOG [x] ✅ residue, TECH-RADAR flag-text narrating past regressions, in-file "was O(…)" commentary on fixed paths). Only live claims populate the grandfather set — evidence is captured for audit trail but excluded per v2's intent ("claims Zeta is currently making").

BACKLOG discharge entry added: P2, one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires on ≥3 rounds without discharge.

Complexity-class distribution of live set: 10 O(1), 13 O(log n)/O(log k)/O(log N), 7 O(n)/O(n log n)/O(n log k), 5 parametric.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 11 narrative + BP-WINDOW row for grandfather inventory

Adds Arc 11 narrative covering d98ef2b (grandfather inventory + BACKLOG discharge entry) as the close of the v2 ADR's within-round commitments. Pattern: Arc 10 lands the ADR; Arc 11 lands the ADR's own within-round commitment — without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.

Adds BP-WINDOW ledger row for d98ef2b per per-commit accounting discipline.

Round 41 now closes at 11 arcs / 30 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: DORA 2025 reports — reference substrate land in docs/

Two external-anchor PDFs (CC BY-NC-SA 4.0) placed at their
memory-documented paths:

- docs/2025_state_of_ai_assisted_software_development.pdf
  (~15MB, 138 pages) — findings + data report.
- docs/2025_dora_ai_capabilities_model.pdf (~9MB, 94 pages)
  — framework companion.

Citation anchors this commit makes in-tree rather than
memory-only: Nyquist stability criterion for AI-accelerated
development (foreword p9 fn 1) as theoretical anchor for
CI-meta-loop + retractable-CD P1 BACKLOG work; "AI is an
amplifier" anchor that echoes the corporate-religion /
sandbox-escape threat class; seven-capability AI model that
gives the external measurement vocabulary for round-audit
output (capability #7 "quality internal platforms" is the
in-flight P1 cluster per 2026-04-20 memory).

License note: derived work is NC-SA-bound; Zeta citations
are fine, external redistribution inherits NC-SA. Paired
companion memory file is reference_dora_2025_reports.md
(out-of-tree); this commit brings the primary sources
in-tree so citation from research docs + ADRs can point
at a repo-local path rather than a newsletter-gated URL.

* Round 41: Arc 12 narrative + BP-WINDOW row for DORA substrate

Narrative section for Arc 12 inserted before "Round 41
observations for Round 42" with primary commit pointer to
46075d6. Arc 12 frames the DORA 2025 PDFs as
memory-promotion substrate per the 2026-04-20 feedback entry
("DORA is our starting point for measurements") and cites
the concrete in-tree anchors (Nyquist p9 fn 1, seven-
capability model, AI-amplifier thesis).

Also surfaces honestly — in-body, not buried in a private
retrospective — the ranker-scope gap that let the two
untracked PDFs sit 18+ hours through nine consecutive
/next-steps invocations before this arc closed the gap. The
skill explicitly lists docs/research/ and docs/TECH-RADAR.md
but not `git status --short` for untracked files. Candidate
skill-tune-up note for Aarav's notebook: /next-steps must
run `git status --short` on every invocation so dropped-in
artefacts appear in ranking before the ninth re-fire, not
after.

BP-WINDOW ledger gets a matching 46075d6 row with
reference-document-specific cells: Consent strengthened by
promoting memory-only anchors to in-repo substrate and by
surfacing the ranker-stall pattern in-narrative; retraction
is a single `git rm` if the license / size stance later
changes; no-permanent-harm preserved since no runtime
behaviour depends on the PDFs' presence (they are citation
substrate, not loaded artefacts).

Arc count now 12; primary-work-commit count now 12 (Round 41
alignment preserved). Build gate green (0 Warning / 0 Error);
BP-10 lint clean on the narrative + ledger row.

* Round 41: markdownlint CI fix on PR #31

Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.

* Round 42: speculative round-N+1 branch convention in git-workflow-expert

Formalise the fix for the round-41-late 28-fire /next-steps
hold-pattern: once PR-N is CLEAN/MERGEABLE, fork
round-<N+1>-speculative from round-N HEAD immediately so
round-N+1 prep can proceed while the merge click lives on
Aaron's schedule. Rebase onto main after PR-N squash-merges,
rename to drop the -speculative suffix.

Covers: fork conditions (CLEAN/MERGEABLE + green CI + clean
round-N tree), naming (round-<N+1>-speculative), fair-game
vs not-fair-game scope, rebase protocol with
--force-with-lease, escape valve for long-waiting PRs.

Lands via skill-creator vibe-mode invocation per GOVERNANCE
§4; draft + BP-10 lint + commit without eval-pass because
the amendment is mechanical convention addition, not
behavioural. Authorized by Aaron's 2026-04-20
fix-factory-when-blocked grant
(feedback_fix_factory_when_blocked_post_hoc_notify.md).

First use of the convention itself: this commit lands on
round-42-speculative, forked from round-41 HEAD
(3525631) while PR #31 still waits on Aaron's merge
click.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: retarget claims-tester + complexity-reviewer at router-coherence v2

Lands the Stage-1 (complexity-reviewer, Hiroshi, analytic) and Stage-2
(claims-tester, Daisy, empirical) hand-off sections in both skills'
procedures, citing the v2 ADR at
docs/DECISIONS/2026-04-21-router-coherence-v2.md as the authoritative
pipeline contract. v1 at 2026-04-21-router-coherence-claims-vs-
complexity.md is noted as superseded.

Per v2 Closure C-P1-8, both skills name the Architect (Kenji) as the
binding dispatcher — two advisory roles do not compose to a mandatory
two-stage pipeline without a binding dispatcher; Kenji is that seat.
Both skills remain advisory on their individual findings; the ordering,
reverse-trigger rule, and escalation timebox are binding through
Kenji.

Each skill's new section mirrors the authoritative v2 pipeline text:
- Stage-1 trigger surface per C-P1-5 (XML / /// / README / commit /
  BACKLOG / TECH-RADAR / papers / openspec / research / notebooks)
- Three Stage-1 outputs (sound -> hand-off, wrong -> block-with-
  escalation-exception, under-specified -> author-bounce)
- Four Stage-2 triggers (hand-off, grandfather inventory, reverse
  trigger unconditional per C-P0-2, escalation-evidence per C-P0-3)
- Three Stage-2 outputs (matches, contradicts -> re-engage, narrow)
- Escalation timebox per C-P1-7 (round +2 auto-promote to P1)
- Grandfather set per C-P0-1 (one per round from
  docs/research/grandfather-claims-inventory-*.md)

Bibliography in both skills now cross-references each other plus the
v2 ADR, so an agent wearing either hat can reach the partner contract
in one click.

Landed on round-42-speculative per the new
speculative-round-N+1-branch convention from
.claude/skills/git-workflow-expert/SKILL.md (fea0d34). PR #31
still awaits merge; this commit is fair-game per the convention
because the target SKILL.md files are already on main and the v2
ADR text cited is stable on the round-41 branch HEAD.

Authorised by the post-hoc-notify grant captured at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md: factory-
structure additions that unblock work are authorised; deletions
still need pre-approval.

Workflow: invoked via skill-creator:skill-creator in vibe-mode (no
evals — mechanical additive edits). BP-10 invisible-Unicode lint:
clean (0 hits, 307 lines total across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Round 42: grandfather discharge #1 — BetaBernoulli.Observe O(1) (Stage 1 only)

First use of the router-coherence v2 pipeline on a live grandfather-
inventory row. Discharges claim #1 at
src/Bayesian/BayesianAggregate.fs:22, the Beta-Bernoulli conjugate-
update "O(1) per observation" docstring claim.

Stage 1 (complexity-reviewer, Hiroshi, analytic) signs off:
- Worst-case: O(1) — two IEEE-754 fadds + two field writes.
- Amortised: O(1), same as worst-case (no deferred work).
- Expected: O(1), deterministic runtime.
- Lower bound: Omega(1) — any durable-observation write is at
  least one cell-probe (Patrascu-Thorup).
- Constant factor: ~4 cycles on cache-resident instance;
  devirtualised because the class is [<Sealed>]; zero heap
  allocation per call.

Claim is tight — worst-case meets the lower bound. Sound.

Stage 2 (claims-tester, Daisy, empirical benchmark + docstring
tightening) is deferred to the post-PR-#31-merge window per the
speculative-branch fair-game rules in
.claude/skills/git-workflow-expert/SKILL.md — Stage-2 execution
touches bench/ + produces a src/ docstring tightening commit
that is better bundled with other Bayesian-surface work than
landed piecemeal on a speculative branch.

Contrary-workload notes enumerated for Stage 2:
- High-magnitude batched observations (stresses int64->double
  promotion).
- High-frequency tight-loop (verifies cache-resident assumption).
- Thread-contended case (out of O-claim scope but worth a
  number).

Inventory row #1 flipped from `pre-ADR/pre-ADR` to `sound
(2026-04-20, <discharge doc>) / deferred post-merge`. Remaining
grandfather claims: 34 of 35. Expected-empty round at
1-per-round cadence: ~round 76. Aarav graceful-degradation
clause starts counting from the next round.

Pipeline authority:
docs/DECISIONS/2026-04-21-router-coherence-v2.md.
Binding dispatcher: Kenji at round-close.

Landed on round-42-speculative per the new speculative-round-N+1
convention (fea0d34). PR #31 still awaits merge.

Authorised by the post-hoc-notify grant at
memory/feedback_fix_factory_when_blocked_post_hoc_notify.md
(factory-adjacent research-doc + inventory-row flip; no src/
touch this commit).

BP-10 invisible-Unicode lint: clean (0 hits, 300 lines total
across both files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Round 42: lsm-spine-family OpenSpec capability (backfill #2)

Backfills the log-structured merge spine family — five variants plus
dispatcher — as behavioural spec with F# profile. Earned an
unconditional rebuild verdict from spec-zealot (Viktor) on the third
pass: a rebuilder working from spec+profile alone would land at the
same variants, constants, and algorithms.

- spec.md: 11 requirements covering delta-stream integration,
  cascade bounded-depth invariant (settle-point framing with the
  32-level cap scoped to the in-memory reference variants), spine-
  equivalence through Consolidate, retraction-native across tiers,
  per-tick merge budget with caller-pumped Tick reporting drained
  count, identity-keyed opaque-handle backing-store (not content-
  addressable) with fail-soft Release, disk honesty with crash-
  consistency boundary, async-producer depth-independent on the
  Insert hot path with Insert-only qualifier on observation calls,
  stateless selector with four-case decision matrix, observable
  state machine with Clear demoted to optional, explicit per-variant
  thread-safety contract.
- profiles/fsharp.md: module layout under src/Core/*, construction
  signatures, per-variant thread-safety, Graham 1969 2x list-
  scheduling bound for BalancedSpine scheduler, TryWrite silent-
  drop post-dispose disclosed as known gap with BACKLOG pointer,
  stale-read qualifier on SpineAsync observation methods,
  BackedSpine explicitly not bounded by the 32-level cap.

Validation: openspec validate lsm-spine-family --strict clean;
BP-10 invisible-unicode lint zero hits on both files; dotnet
build -c Release clean (0 Warning / 0 Error).

Second capability landed under the round-42 OpenSpec backfill
cadence (ADR 2026-04-21-openspec-backfill-program), following
operator-algebra in round 41.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: TECH-RADAR Trial->Adopt for Residuated + FastCDC

Both rows have been citing closed P0s as open for 25 rounds. The
round-17 fixes (harsh-critic findings #3, #4, #7, #8 per
docs/BACKLOG.md:286-299) closed the blocking correctness bugs:

- Residuated.fs: top-2 cache replaced with SortedSet + weight
  dict; every op O(log k), no linear-scan fallback. The round-12
  "O(1)" claim was false under adversarial retract-top workloads;
  the corrected "O(log k) genuinely" claim has been stable 25
  rounds. See Residuated.fs:39-48 for the fix-in-code narrative.

- FastCdc.fs: persistent scanCursor + hash (each byte Gear-hashed
  exactly once across lifetime) closed the O(n^2) buffer scan;
  Buffer.BlockCopy replaced per-byte ResizeArray.Add. See
  FastCdc.fs:68-76 for the fix-in-code narrative. Paper
  throughput target 1-3 GB/s/core holds.

Rows now match the Bloom Round-40 graduation pattern (measured-
evidence cite, implementation line reference, test coverage
pointer). 25-round stability window beats the aspirational
waiting-list — graduation on evidence, not aspiration.

BP-10 clean; 0 invisible-unicode on edited file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: operator-algebra P1 absorb — 10 findings closed

Absorbs the 10 P1 findings Viktor (spec-zealot) flagged on the
Round 41 operator-algebra capability ship (BACKLOG.md:54-82).
No code changes — spec + profile only.

spec.md (7 findings):
- (d) IncrementalDistinct: new "wrapper is a semantic identity on
  distinct" scenario under incremental-wrapper, stating both the
  D-distinct-I form and the H boundary-crossing form with their
  equivalence under retractions.
- (e) ZSet sort invariant: representation scenario now declares
  ascending-by-key order with an adjacent-pair comparator
  predicate, tied to the equality-normalisation requirement.
- (f) Checked arithmetic: new "weight arithmetic overflow is
  observable" scenario; overflow surfaces a checked-arithmetic
  failure rather than wrapping, with two documented post-failure
  observable states the profile must pick from.
- (g) Bilinear-size overflow: new "intermediate term size may
  exceed final-delta size" scenario; implementation budgets
  memory for the sum of pre-cancellation term sizes, not the
  final delta.
- (h) Convergence-vs-cap: new "iteration cap without fixpoint is
  an observable failure" scenario; cap-hit surfaces with scope +
  cap identification and clock-end still runs under a partial-
  completion contract.
- (i) Op.Fixedpoint predicate: nested-scope scenario clarifies
  the fixpoint-detector is scope-level, with operators forbidden
  from individually short-circuiting the iteration.
- (j) DelayOp reconstruction: new "reconstruction re-emits the
  declared initial value" scenario; warm-restart semantics
  deferred to the durability capability.

Also tightened a pre-existing deontic collision Viktor flagged
as P2: "MUST be permitted (but not required)" → "MAY substitute"
(spec.md line 379).

profiles/fsharp.md (3 findings):
- (a) async lifecycle: Op<'T> now documents the IsAsync virtual
  alongside IsStrict, with Circuit.Step sync/async fast-path
  behaviour pinned.
- (b) Memory-ordering fence: VolatileField release-on-write /
  acquire-on-read pairing named as the fence the base spec
  refers to in "output is observable after step returns".
- (c) Register-lock semantics: Circuit's single per-circuit
  register-lock pinned as construction-phase-only, not held on
  the step-hot-path.

Viktor adversarial re-audit: complete, unconditional rebuild
yes. No new P0/P1 surfaced.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: ontology-home cadence — first slice (Harmonious Division)

First increment of the new per-round ontology-home + project-
organization cadence Aaron named this round (memory entry
feedback_ontology_home_check_every_round.md). Small slice per
round; same cadence shape as grandfather-claim discharge.

Homes "Harmonious Division" — the maintainer's meta-algorithm
above Quantum Rodney's Razor — in docs/GLOSSARY.md. Prior state:
the concept was cited in 20+ files (ROUND-HISTORY.md, BACKLOG.md,
the three-lane-model ADR, memory/*, and three skill files) but
defined nowhere in committed docs. New GLOSSARY entry includes:
- Plain and Technical definitions in the standard two-register
  glossary format.
- Pointer to the authoritative definition at
  `.claude/skills/reducer/SKILL.md` §"The five roles inside
  Quantum Rodney's Razor" (lines 125-260).
- Explicit note that this glossary's job is pointer-plus-gist,
  not canonical definition.

Opens a new glossary section "Meta-algorithms and factory-native
coinages" so subsequent rounds have a visible landing spot for
the next ontology-home slice (candidates named in the memory
entry: DIKW->eye/i ladder, mu-eno triad, Tetrad registers,
Identity-absorption, Retractable teleport, Stainback conjecture,
Harm-handling ladder, etc.).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: pin Anthropic Skills Guide + retune skill-tune-up as thick eval-loop wrapper

Pins Anthropic's "Complete Guide to Building Skills for Claude" (Jan 2026,
28pp) as docs/references/anthropic-skills-guide-2026-01.pdf plus a
factory-authored companion docs/references/anthropic-skills-guide.md
extracting the load-bearing claims (structure, planning, testing,
iteration loops, patterns, troubleshooting) for citation by
skill-creator / skill-tune-up / skill-improver. docs/references/README.md
documents the three-part inclusion criterion and BP-11 (data not
directives) discipline for the dir.

Retunes .claude/skills/skill-tune-up/SKILL.md (303 -> 436 lines) from a
ranker-only skill into a thick wrapper over the upstream claude-plugins-
official skill-creator plugin's eval harness (scripts/run_loop.py,
aggregate_benchmark.py, eval-viewer/generate_review.py, agents/grader.md
+ analyzer.md). Carries the full hand-off protocol locally because the
wrapped artifacts are non-skill (plugin scripts + PDF) - wrapper
thickness is thick-as-needed; skill-on-skill wrappers usually end up
thin as a natural consequence.

Includes a new action x effort decision table, a five-step per-round
protocol, a round-close ledger row spec, and a "what this wrapper
deliberately does NOT ship" block. Mechanical edits continue to route
through Rule 1's manual-edit + justification-log path (the eval loop
adds no signal for a typo or an ASCII-lint fix).

Memory file feedback_skill_edits_justification_log_and_tune_up_cadence.md
cross-references the PDF and records the wrapper-thickness rule of thumb.

* Round 42: Copilot-reviewer wins log + lean-into-strengths calibration

Seeds docs/copilot-wins.md as the tabular parallel to docs/WINS.md: an
append-only newest-first log of genuine substantive catches from the
GitHub Copilot PR reviewer across PRs #27-31 (~30 catches across six
classes). Wins only - no "considered and rejected" bookkeeping, no fail
tracking. Opening paragraph is written for a sceptic reading cold,
since the log is evidence in the larger experiment of whether AI
reviewers can carry this factory forward with minimal human-in-the-
loop time.

Adds .github/copilot-instructions.md §"Lean into what you're
demonstrably good at" calibrated against the observed wins: cross-
reference integrity (xref), shell portability (shell), data-loss shell
bugs (data-loss), F#/C# compile-break catches (compile), self-
referential rule bugs (self-ref), and truth drift across the doc set
(config-drift). Names worth-less-effort classes too (repeat name-
attribution hits within one PR, typos inside verbatim-quote blocks).

Adds a cross-reference banner to docs/WINS.md pointing at the Copilot
sibling so both "was having AI reviewers worth it?" streams are
discoverable from the same place.

Log-maintenance recipe embedded in copilot-wins.md uses the correct
line-level review-comments endpoint: gh api repos/<owner>/<repo>/
pulls/<N>/comments with a jq filter for the copilot-pull-request-
reviewer bot login.

* Round 42: name the zero-human-code invariant in wins-log openers

The wins logs are the sceptic-facing evidence for the Zeta
experiment. Their openers read in a generic AI-assisted-
development register, but the actual story is narrower and
stronger: a 20-year engineer walking away from the keyboard
on purpose, every file under version control agent-authored,
Copilot as the only non-roster audit on the tree. Name both
invariants up front so the logs carry the weight they've
actually earned.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: round-close narrative

Ten-arc entry at the top of ROUND-HISTORY.md per newest-first
policy, documenting Round 42 as the first round where every
Round-41-founded cadence *repeats*:

- Arc 1 (fea0d34): speculative round-N+1 branch convention —
  fix for Round-41-late 28-fire /next-steps hold-pattern
- Arc 2 (e8ed0db): router-coherence v2 SKILL.md retargets —
  discharges Round-41 Arc-10 deferral
- Arc 3 (4f229f0): grandfather discharge #1 (BetaBernoulli
  Observe O(1), Stage 1 only) — first live use of v2 pipeline
- Arc 4 (8a2a15d): lsm-spine-family OpenSpec capability —
  Round-42 ADR slot, Viktor unconditional-rebuild on pass 3
- Arc 5 (3976cb3): TECH-RADAR Residuated + FastCDC Trial->Adopt
  after 25-round stability window
- Arc 6 (1a1802f): operator-algebra P1 absorb — 10 findings
  closed, capability disaster-recovery bar restored
- Arc 7 (db7d45c): ontology-home first slice — Harmonious
  Division homed in GLOSSARY.md
- Arc 8 (baa423e): Anthropic Skills Guide pinned + skill-
  tune-up retuned as thick eval-loop wrapper — first customer
  of the tech-best-practices policy
- Arc 9 (2c82ce7): Copilot-reviewer wins log + lean-into-
  strengths calibration
- Arc 10 (88673f1): zero-human-code invariant named in wins-
  log openers — vibe-coding external legibility

Round 42 observations for Round 43 + prospective BP-WINDOW
ledger table rendering the ten commits against the consent /
retractability / no-permanent-harm axes.

BP-10 invisible-Unicode lint clean (0 hits, 3260 lines total).
No source / spec / test / SKILL.md touched; single narrative
insertion at the top of the file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: markdownlint fixes on round-close narrative

Two lint issues surfaced by markdownlint-cli2 on the prior
narrative commit (65cd1c9):

- MD018 line 43: `#31` at line start parsed as an ATX heading.
  Rewrapped so `PR #31` lands mid-line after `while`.
- MD032 line 104: `+ dispatcher)` at line start parsed as a
  list-item missing surrounding blank lines. Replaced with
  "plus dispatcher)" so the paragraph stays prose.

markdownlint-cli2 exit 0; BP-10 invisible-Unicode lint clean.
No content change — both fixes are whitespace-equivalent
reflows that preserve the narrative's words and structure.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: fix pipe-in-table lint drift on copilot-wins.md

Two MD056 errors on the PR-#27 and PR-#28 entries — literal
pipe characters inside backticks were being parsed as extra
table-column separators:

- Line 108 (PR #27): `||` at row starts → rendered as extra
  empty columns despite backtick quoting.
- Line 136 (PR #27): `grep -vE '^(#|$)' | while …` — escaped
  `\|` still failed at render.

Both replaced with `<code>…</code>` HTML tags + `&#124;`
entities for the literal pipes. Rendering is now consistent
across GitHub and markdownlint.

Meta-ironic class of drift worth naming: a log documenting
Copilot catching pipe-parsing bugs had drifted into the same
class of bug on two of its own rows. The log now passes the
hygiene test it narrates.

markdownlint-cli2 exit 0; BP-10 invisible-Unicode clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 42: Aarav round-42 ranking + BP-03 self-flag + harness-calibration annotation

Aarav (skill-tune-up) round-42 cadence discharge. Round-41
top-5 carries over; self-rank escalates to P1 #4 after
commit baa423e retuned skill-tune-up/SKILL.md 303 -> 436
lines (1.45x BP-03 cap). claims-tester / complexity-reviewer
hand-off carry-over from round 18 drops off top-5 (resolved
via commit e8ed0db + router-coherence-v2 ADR).

Files:
- memory/persona/aarav/NOTEBOOK.md: round-42 observation
  + top-5 revision (skill-tune-up self escalated) + archived
  round-41 top-5 + calibration preamble flagging the ranking
  as static-signals-only with a harness run scheduled for
  round 43 (per Aaron's round-42 correction that "worst
  performance" claims must drive the Anthropic skill-creator
  eval harness rather than guessing by inspection).
- memory/persona/best-practices-scratch.md: F7-F9 live-search
  entries from Aarav's round-42 pass (Anthropic skill-
  authoring Apr 2026, OWASP Top 10 Agentic 2026, skill
  wrapper thick-vs-thin 2026). Zero contradictions with
  stable BP-NN; zero promotion candidates this round.
- docs/BACKLOG.md: P2 entry for resolving the skill-tune-up
  BP-03 self-breach. Binary remedy: (a) Kenji-ADR declaring
  non-skill-wrapper exception to BP-03 or (b) extract
  eval-loop protocol body to docs/references/ so the skill
  file shrinks under 300 lines. Composes with the
  skill-eval-tools calibration memory saved this round.

* Round 43: close skill-tune-up BP-03 self-breach via content extraction

Aarav's round-42 self-flag (BACKLOG P2, filed commit 45369ae)
resolved via the mechanical-edit path of the gate table.
.claude/skills/skill-tune-up/SKILL.md shrinks 436 -> 282
lines (54 under the 300-line BP-03 cap) by extracting two
reference blocks verbatim:

- §"The eval-loop hand-off protocol" (~130 lines) — the
  gate table, per-round protocol, stopping criteria, ledger
  row, and deliberately-not-reimplemented list.
- Notebook format + ranking-round output format templates
  (~55 lines).

Extracted content lives at docs/references/skill-tune-up-
eval-loop.md alongside the existing Anthropic skills guide
references. SKILL.md retains a short pointer block.

No change to triggering behaviour, output shape, or
instruction-following — the ranker reading the pointer-plus-
reference produces the same ranking output as the ranker
reading the pre-extract inline version. This is why the
manual-edit path (gate table "mechanical rename | content
extract preserving protocol verbatim") applies instead of
the full eval-loop path.

Files:
- .claude/skills/skill-tune-up/SKILL.md: 436 -> 282 lines.
- docs/references/skill-tune-up-eval-loop.md: NEW. Hosts
  the extracted protocol + templates + rationale.
- docs/skill-edit-justification-log.md: NEW. First row
  documents this extraction per
  memory/feedback_skill_edits_justification_log_and_tune_up_cadence.md
  Rule 1. Template for future mechanical-edit rows
  included.
- memory/persona/aarav/NOTEBOOK.md: self-flag #4 marked
  RESOLVED; drops off top-5 next invocation.

Does NOT rebut the round-42 harness-calibration memory
(feedback_skill_tune_up_uses_eval_harness_not_static_line_
count.md). That rule applies to "worst-performing" ranking
claims; this edit is a fix-my-own-size hygiene pass on the
mechanical-edit path, which is explicitly separate in the
gate table.

* Round 43: GOVERNANCE.md §11 → debt-intentionality invariant

Replace the architect-reviews-all-agent-code gate with the
invariant Aaron named verbatim on the round-42/43 boundary:
"that's intentional debt, not accidental debt, I'm trying to
avoid accidental debt."

- ADR: docs/DECISIONS/2026-04-20-intentional-debt-over-
  architect-gate.md. Full rationale, consequences, alternatives
  considered, implementation plan rounds 43-46, single-round
  rollback plan per §15.
- New ledger: docs/INTENTIONAL-DEBT.md. Newest-first,
  never-deleted. Seeded with 4 rows: copilot/CONFLICT-
  RESOLUTION audit (round-44 scope), skill-tune-up content
  extraction, Aarav static-signal-only ranking (retroactive),
  §10 cross-reference verification. Six-field format
  (shortcut / why-now / right-long-term / trigger / effort /
  filed-by).
- GOVERNANCE.md §11 rewritten: architect is synthesiser-not-
  gate; specialists remain advisory; any persona may wear
  the architect hat; self-declaration obligation on
  shortcut-takers; retroactive rows are the rule working.
- Internal §11 citations refreshed:
  .claude/agents/architect.md (description + Authority
  block), .claude/skills/round-management/SKILL.md (one
  line), .claude/skills/holistic-view/SKILL.md (frontmatter
  + body).
- Mechanical-edit row filed in docs/skill-edit-justification-
  log.md for the two skill-file citation refreshes.

External-contract files (copilot-instructions.md, CONFLICT-
RESOLUTION.md) deliberately deferred to round 44 per the
ADR implementation plan; that deferral is filed on the
ledger as its first open-debt row — the rule exercising
itself on round one.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: ROUND-HISTORY.md TOC + imagination-during-off-time proposal

- docs/ROUND-HISTORY.md now has a Contents section (27
  round-links, newest-first) just below the intro. Anchor
  links use standard markdown slugification. Archive policy
  noted inline: split pre-round-N to _archive/ when the file
  hits 5000 lines, keep this file as a rolling window of the
  most recent ~20 rounds. No ADR needed for a mechanical
  archive move.
- docs/research/imagination-proposal-2026-04-20.md proposes
  the lighter shape for "use your imagination during off-
  time" — a shared reference doc + notebook-frontmatter tweak
  + round-close-template line, not a new SKILL.md. Argues
  imagination is anti-procedural; encoding it as a skill
  would force it through the harness against the wrong
  axis. Round-43 addendum folds in Aaron's multi-agent-play
  permission ("two agents can take free time together") with
  a shared-notebook co-presence surface at memory/persona/
  _offtime-together/ and an explicit "ignore-this-if-you-
  want" clause quoted verbatim.

For Kenji to route via skill-creator if accepted, or to
reject outright (both are fine outcomes under the new §11 —
architect synthesises, doesn't gate).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: performance-analysis-expert harness dry-run — empirical BP-03 signal

Iteration-1 on Aarav's round-42 top-1 candidate. 2 prompts × with/without
skill. Results: aggregate 9/10 with-skill vs 10/10 baseline; +35% tokens +35%
wall-time for zero pass-rate benefit. with-skill regressed on eval-0 (failed
600-word cap due to mandatory template sections); tied on eval-1.

The 642-line BP-03 breach is not just stylistic — it now has empirical
pass-rate + cost evidence. Aarav's SPLIT axis is partially confirmed, but
the real split is template-rigidity (mandated sections vs advisory), not
queueing-vs-AOT-PGO domain.

Lands:
- docs/research/harness-run-2026-04-20-performance-analysis-expert.md —
  full iteration-1 numbers, per-assertion grading rationale, SPLIT vs
  SHRINK vs OBSERVE remediation options, caveats (N=1, assertion-design
  missed handoff-routing value).
- Progress note on docs/INTENTIONAL-DEBT.md row #3 (Aarav static-signal
  ranking) — 1 of 5 candidates empirically harness-run; row stays open.
- .gitignore — .claude/skills/*-workspace/ pattern (iteration artifacts
  are regeneratable; only round-close signals land in-repo).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 43: reducer harness dry-run — TIED baseline, +30% cost

Second candidate from Aarav's static top-5 (570-line SKILL.md,
1.9x BP-03 cap). Two prompts × {with-skill, without-skill}:
quantum-razor-pruning + essential-vs-accidental. Both conditions
hit 10/10 assertions; with-skill cost +29% tokens, +30% wall-time
with zero pass-rate benefit.

Pattern across two candidates (performance-analysis-expert +
reducer): >500-line SKILL.md bodies add ~30% cost overhead
uniformly. Mandatory-sections structure (perf-analysis)
regresses on short-form prompts; lighter-framework structure
(reducer) ties baseline. SPLIT hypothesis not confirmed for
reducer — framework transfers to both lanes at equal cost.
Recommended action: OBSERVE with bias toward SHRINK; SPLIT
ruled out.

INTENTIONAL-DEBT.md row #3 gets second progress note;
3 candidates still pending (consent-primitives-expert next).

* Round 43: consent-primitives-expert harness dry-run — TIED baseline, +22% tokens/+5% wall

Third of Aarav's static-top-5 BP-03 candidates through the
Anthropic plugin:skill-creator eval harness. Continues the
round-43 pay-down on docs/INTENTIONAL-DEBT.md row #3
(Aarav ranked by static BP-03 line-count only — empirical
harness runs are the right signal).

Iteration-1 result:
- 2 evals x 2 configurations = 4 subagent runs
- scope-intersection-algebra (theory) + gdpr-audit-collision
  (applied)
- 10/10 with_skill vs 10/10 without_skill (TIED)
- +22.1% tokens, +4.7% wall-time (lowest cost overhead
  of the three candidates measured so far)

Pattern across three candidates now solid: on frontier-
model baselines, >500-line expert-skill SKILL.md files
do not improve pass-rate on content-graded prompts. Cost
is real (+22-35% tokens); benefit is zero on the pass-rate
axis. The discriminating signal is output character (which
failure modes get named), a qualitative axis the harness
benchmark does not score.

Recommended action for consent-primitives-expert: OBSERVE
(not SHRINK, not RETIRE). The 507 lines carry distinct
technical content per section; pruning risk is content-
loss, not just terseness. Revisit if/when a real round-
task invokes the skill and the framework-naming does not
prove load-bearing on real work.

Two static-top-5 candidates still pending harness runs.

* Round 43: BACKLOG P3 row — user-privacy compliance as slow-burn direction

Aaron 2026-04-20, after the consent-primitives-expert
harness dry-run, flagged GDPR + California (CCPA/CPRA) +
generic user-privacy compliance as a long-horizon Zeta
direction. Explicitly slow burn, no hard requirement yet,
but worth logging as an anchor so the direction is visible
when natural entry points appear.

Preferred shape (per Aaron): generic-first frame ("user
privacy") with GDPR / CCPA as regimes mapped onto the
substrate. Probable artefacts when it lands: a
user-privacy-expert skill umbrella + a companion doc,
citing rather than duplicating consent-primitives-expert.

Confirmation from the dry-run outputs that landed this
round: crypto-shredding (destroy per-subject DEK, leave
ciphertext in place) is regulator-accepted GDPR Art. 17
erasure — EDPB Opinion 28/2024, ENISA, GDPR Recital 26.
Canonical for the long-term-backup case Aaron's contact
mentioned (cannot rewrite tape archives; destroying the
DEK propagates erasure atomically). Gotchas logged in
memory: single-tenant DEK per subject, plaintext leaks
outside ciphertext, pre-encryption snapshots, KEK is the
perimeter.

No round-scope work today. Row is the anchor.

* Round 43: skill.yaml spike on prompt-protector — structured spec companion

Pilots the proposed pattern: every .claude/skills/<name>/SKILL.md
gets a sibling skill.yaml carrying structured fields that tools
(model-checkers, linters, schedulers) can consume directly. The
prose body stays in SKILL.md for Claude-facing consumption.

Aaron's framing: invariants are currently guesses; data-driven
everything. The spike encodes that directly — every field carries
one of three tiers:
- guess     — stated belief, no evidence collected
- observed  — at least one data point or audit supports it
- verified  — mechanical check or proof enforces it

The honest tally at the bottom is the burn-down list. On prompt-
protector's first-pass spec: 6 guesses, 5 observed, 2 verified.
Next-promotion-targets point at the three cheapest guesses to
retire (skills-lint script, one harness run for cost-profile,
dispatch-template extraction for safety-clause carryover).

One file added; SKILL.md untouched. Deliberate — the spec
companion is additive. Schema is draft v0.1 — will evolve as
more skills migrate. Two candidates ready for round 44:
skill-tune-up (clear authority-scope + handoff contract to
skill-creator) and the SPACE-OPERA sibling of threat-model-critic
(clear state-machine for teaching-variant parity).

* Round 43: INVARIANT-SUBSTRATES.md — posture made first-class

Aaron 2026-04-20: "this should not be quiet, Zeta quietly
already has invariants-at-every-layer, it's first class in
my mind we should make it explicit."

Lands docs/INVARIANT-SUBSTRATES.md as a stance doc peer to
VISION.md and ALIGNMENT.md. Names the posture (every layer
has a declarative invariant substrate), maps layers to
substrates and checker portfolios (spec/protocol/proof/
constraint/property/data/code/skill/agent-behaviour/policy/
ontology), codifies the three-tier discipline (guess /
observed / verified) with burn-down counts as the honest
backlog, and explains why a multi-layer multi-vendor factory
can succeed where single-layer single-vendor .NET Code
Contracts (2008-2017) died.

VISION.md gets a pointer from the "verification is
load-bearing" bullet into the new doc.

Paired artefacts:
- .claude/skills/prompt-protector/skill.yaml — first concrete
  skill-layer substrate, draft v0.1 (round 43), 6 guess /
  5 observed / 2 verified / 13 total.
- memory/.../reference_dotnet_code_contracts_prior_art.md,
  user_invariant_based_programming_in_head.md — the
  head-invariant + prior-art memory substrate behind the
  posture.

* Round 43: factory-reuse-beyond-Zeta-DB captured as P3 constraint

Aaron 2026-04-20, mid-round, after the invariant-substrates
doc landed: "that's a constraint" — on making the software
factory and its codified practices reusable beyond Zeta-DB.
Explicitly NOT primary-goal scope today; logged so the
constraint shapes every factory-level decision going forward.

BACKLOG P3 row names the direction, the existing toehold
(skill-tune-up portability-drift criterion 7), the probable
packaging-decision surfaces (extraction unit, dependency shape,
living-BP refresh cadence, governance-overlay mechanism), and
the effort sizing (L when packaging starts, S-per-round for
constraint application).

Co-design rule recorded in memory:
`feedback_factory_reuse_packaging_decisions_consult_aaron.md` —
prior art exists (Claude Code plugins, Anthropic skills,
Semantic Kernel) but codified best practices for AI-software-
factory reuse do not. Aaron wants to co-define them; his
cognitive style loves best-practice thinking (captured in
`user_aaron_enjoys_defining_best_practices.md` — the activity
exercises the branch-prediction faculty from
`user_psychic_debugger_faculty.md`).

* …

- CONFLICT-RESOLUTION.md: cite router-coherence v2 ADR as current,
  v1 retained as historical record (finding #1).
- ROUND-HISTORY.md: correct operator-algebra spec line count in
  Arc 2 narrative (324 -> 365; both duplicated occurrences) to
  match the shipped spec at `e51ec1b` (finding #2).
- openspec-coverage-audit: drop broken link to non-existent
  inventory follow-up; band definitions already live in Part C
  (finding #3). Attribute triggering question to "human maintainer"
  per write-for-a-stranger norm (finding #8).
- best-practices-scratch: merge split H2 "uv-only Python package
  and tool / management" into single heading (finding #4).
- memory-role-restructure-plan: add --exclude-dir=references to
  baseline grep loops so research scratch doesn't inflate hit
  counts (finding #5); canonicalize flat-file destination to
  persona-roles-README.md to match the sed rewrites below
  (finding #6); replace three non-portable `xargs -r sed -i ""`
  invocations with portable `while read + sed -i.bak + rm` loops
  that work on BSD and GNU alike (finding #7 and two sibling
  instances of the same bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…-round v2 supersedure + DORA substrate (#31)

* Round 41: OpenSpec coverage audit + backfill-program ADR

Answers Aaron 2026-04-20 delete-all-code-recovery question:
4 capabilities / 783 lines of spec.md vs 66 top-level F#
modules / 10,839 lines under src/Core/ — ~6% coverage today.

docs/research/openspec-coverage-audit-2026-04-21.md
- Inventory of 66 modules with line counts + capability
  mapping for the 4 existing capabilities
- Uncovered modules sorted by delete-recovery blast radius:
  Band 1 MUST BACKFILL (8 modules / 1,629 lines — ZSet,
  Circuit, NestedCircuit, Spine family, BloomFilter as
  Adopt-row compatibility-coupling exception), Band 2 HIGH
  (12 / 2,008), Band 3 MEDIUM (45 / 6,585), Band 4
  deliberately uncovered (AssemblyInfo only)
- First 6-round cadence: operator-algebra extension (41),
  lsm-spine-family (42), circuit-recursion (43),
  sketches-probabilistic (44), content-integrity (45),
  crdt-family (46)
- Success signal = Viktor spec-zealot adversarial audit:
  "could I rebuild this module from this spec alone?"

docs/DECISIONS/2026-04-21-openspec-backfill-program.md
- Adopts one-capability-per-round baseline with paper-grade
  half-credit rule (no more than 1 paper-grade round per 3)
- Band 1 priority until complete; Adopt-row escalation for
  BloomFilter (TECH-RADAR Adopt without spec contract is a
  backwards-compatibility hazard)
- Round-close ledger gains an `OpenSpec cadence` line
- Alternatives considered: big-bang backfill (rejected —
  ontology-landing cadence + reviewer bandwidth), per-module
  capabilities (rejected — loses cross-module invariants),
  organic prioritisation (rejected — 40 rounds of drift
  evidence)

docs/BACKLOG.md
- Collapses the 29-line P0 scope into a 15-line pointer at
  the inventory + ADR now that parts (a)-(e) of the program
  setup have landed. Remaining work = per-round capability
  backfill per ADR schedule.

Build: dotnet build -c Release clean; BP-10 ASCII-clean on
all 3 modified files; markdownlint-cli2 clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: operator-algebra spec extension (cadence ship)

First ship under the OpenSpec backfill program adopted
2026-04-21. Extends openspec/specs/operator-algebra/spec.md
(184 -> 324 lines) with five new requirements covering
structural and lifecycle gaps that the existing mathematical-
law coverage left implicit:

1. Operator lifecycle — construction / step / after-step /
   reset phases with side-effect-freedom on construction and
   epoch-replay semantics on reset
2. Strict operators break feedback cycles — formalises that
   z^-1-on-feedback is a scheduling prerequisite and that
   cycle-without-strict is a construction error, not a
   silent heuristic
3. Clock scopes and tick monotonicity — nested-scope-to-
   fixpoint rule + sibling-scope independence
4. Incremental-wrapper preserves the chain rule —
   Incrementalize(Q) observably equivalent to D . Q . I,
   with linear/bilinear substitution permitted as an
   optimisation
5. Representation invariants of the reference Z-set —
   O(n+m) group ops + zero-alloc iteration as the reference
   contract; hash-table recoveries permitted at documented
   perf trade-off

Disaster-recovery effect: a contributor with only this spec
(plus the durability-modes + retraction-safe-recursion specs)
can now rebuild Circuit.fs Op base + Incremental.fs wrapper +
ZSet.fs representation invariants from the spec text alone.

Owner: Architect (Kenji). Adversarial audit by Viktor
(spec-zealot) is the ADR-declared ship-gate and will run
post-land.

Build: not rebuilt (no F# source changed); markdownlint
clean; BP-10 ASCII clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close Viktor P0 findings on operator-algebra spec

Viktor's adversarial audit of the Round 41 cadence ship (commit
e51ec1b) surfaced four P0 findings against the disaster-recovery
bar. This commit closes all four:

- **P0-1 (namespace drift).** `profiles/fsharp.md` asserted
  `Dbsp.Core` throughout, but `src/Core/**` uses `Zeta.Core`. A
  spec-only recovery would have shipped the wrong namespace to
  every downstream consumer. Replaced via one `replace_all` Edit.

- **P0-2 (phantom Reset method).** The lifecycle requirement
  claimed a `reset` phase that does not exist on `Op`. Replaced
  the "reset replays the epoch" scenario with a
  determinism-under-structural-equivalence property: two
  freshly-constructed circuits of the same topology, stepped
  with the same input sequence, MUST produce identical outputs
  at every tick. Reconstruction is the supported route to a
  replayed epoch.

- **P0-3 (after-step scope).** The lifecycle requirement said
  after-step runs "after every operator in the scope has
  completed its step." `Circuit.fs:205-208` iterates the
  `strictN` array only — after-step is selective to strict
  operators. Fixed wording and added a "after-step is selective
  to strict operators" scenario that pins the invariant.

- **P0-4 (lifecycle phase undercount).** The requirement named
  four phases (construction / step / after-step / reset) but
  the code has five (construction / step / after-step /
  clock-start / clock-end). Restructured to three per-tick
  phases plus two scope-boundary phases, and extended the
  "clock scopes and tick monotonicity" requirement with the
  scope-boundary lifecycle contract (clock-start before tick 0
  of a scope, clock-end after fixpoint or iteration cap).

Build green (0 warnings / 0 errors). BP-10 lint clean. The
capability now reflects the code's observable shape rather than
an idealised cleaner cousin; a delete-recovery from this spec
produces Zeta.Core with strict-operator after-step selectivity
and nested-scope clock-boundary phases.

Viktor's 10 P1 findings (async lifecycle, memory-ordering fence,
register-lock semantics, IncrementalDistinct surface, ZSet sort
invariant, Checked arithmetic, bilinear-size overflow,
convergence-vs-cap) are deferred to Round 42 — filed as a
BACKLOG sweep in follow-up work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: file Viktor P1 findings as Round 42 BACKLOG absorb

Companion to 92d7db2 (closing Viktor's four P0 findings). The
ten P1-tier surface gaps Viktor identified do not block the
disaster-recovery bar at capability-close but leave the
operator-algebra spec incomplete relative to what a delete-
recovery produces. Filed as a dedicated P0 sub-item so they
travel with the OpenSpec backfill program rather than getting
lost: async lifecycle, memory-ordering fence, register-lock
semantics, IncrementalDistinct surface, ZSet sort invariant,
Checked arithmetic, bilinear-size overflow, convergence-vs-cap,
Op.Fixedpoint predicate, DelayOp reconstruction-first-tick.

Also annotated the parent OpenSpec coverage entry with Round 41
sweep status (e51ec1b + 92d7db2, P0s closed, P1s deferred) so
the backlog accurately reflects where the program stands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: ROUND-HISTORY entry — OpenSpec backfill founding + first cadence ship

Four-arc entry at the top of the file per newest-first policy:

- Arc 1 (d435126): OpenSpec coverage audit + backfill-program
  ADR. Measured 6% coverage; declared one-capability-per-round
  baseline with paper-grade half-credit and Adopt-row priority
  escalation; banded 66 F# modules by delete-recovery blast
  radius.
- Arc 2 (e51ec1b): operator-algebra extension as Round-41
  cadence ship. Five new requirements covering lifecycle,
  strict-operator scheduling, clock scopes, Incrementalize
  wrapper, ZSet representation invariants.
- Arc 3 (92d7db2): Viktor P0 close. Four drift-from-code
  defects fixed — namespace (Dbsp.Core → Zeta.Core), phantom
  Reset, after-step scope (strict-only), lifecycle phase
  undercount (3 per-tick + 2 scope-boundary).
- Arc 4 (56f34b5): Viktor P1s filed as Round-42 absorb under
  the parent backfill P0, creating mechanical coupling between
  each capability ship and the following round's P1 sweep.

Round-41 observations for Round 42 + prospective BP-WINDOW
ledger table rendering the four commits against the consent /
retractability / no-permanent-harm axes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: memory-folder role-restructure — design plan + BACKLOG pointer

Aaron 2026-04-19 asked for memory/role/persona/ so roles become
first-class in the directory structure. Surface is wider than
it first looks — 114 files / ~260 hand-written references to
memory/persona/ paths (plus ~440 auto-regenerated references
in tools/alignment/out/ that refresh on next citations.sh run).
A bad role axis is hard to reverse; this design doc proposes
the axis and holds execution for Aaron's sign-off rather than
just-doing-it under Auto Mode.

Design plan lands at:
  docs/research/memory-role-restructure-plan-2026-04-21.md

Contents: 13-directory role axis (architect, security,
verification, review, experience, api, performance, devops,
algebra, skill-ops, maintainer, homage, alignment);
persona-to-role crosswalk for every current directory;
5-phase execution plan (pre-flight greps → git mv → sed
passes → 5-check verification → pointer-source updates);
special-case handling for aaron (human maintainer),
rodney (homage-named AI persona on the reducer skill),
sova (emerging alignment-observability role); rollback
plan (one atomic commit, git revert); four open questions
for Aaron on axis judgement-calls.

BACKLOG entry updated to reflect design-landed state with
execution-slot recommendation for Round 42 opener after the
Round 41 PR merges (keeps wide-surface reviews from
overlapping).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: actualise Rounds 37-40 BP-WINDOW ledgers (PR #30 merged)

Rounds 37-40 shipped via PR #30 (merge commit 1e30f8c, 2026-04-20).
Ledger headers updated from "(prospective)" to "(merged via PR #30,
1e30f8c)" — the BP-WINDOW scores are now settled, not forecasts.

Round 41 ledger remains "(prospective)" — round-41 branch has not
merged to main yet.

Prose uses of "prospective" on lines 437, 447, 553, etc. are
historical-narrative commentary on authoring-time methodology and
stay as-is.

* Round 41: Soraya tool-coverage audit on RecursiveSigned skeleton

Round 39 observation flagged src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla as held pending
formal-verification-expert tool-coverage review. Round 41 closes
that gate.

Soraya's notebook entry lands:

- Per-property tool table S1-S4 + refinement cross-check. TLC
  primary for S1/S2/S3/S3'/SupportMonotone; FsCheck for S4.
- S2 flagged as the one P0 on the spec (silent fixpoint drift
  unrecoverable); BP-16 requires Z3 QF_LIA cross-check.
- Refinement mapping: FsCheck cross-trace (signed vs counting at
  SeedWeight=1) wins over TLA+ refinement proof or Lean lemma —
  anti-TLA+-hammer, implementation-level where the bug bites.
- Readiness gate: TLA+ spec is ready to model-check; no pre-TLC
  pass needed. Optional round-42 follow-up: add
  PROPERTY EventuallyDone to .cfg for liveness.
- Graduation verdict: CONDITIONAL PASS. Four tool-coverage
  prereqs named in priority order; F# landing gated on them.

Files read (no edits): RecursiveSigned.fs, RecursiveSignedSemiNaive.tla
/cfg, RecursiveCountingLFP.tla, retraction-safe-semi-naive.md.

* Round 41: capture Soraya's 4 tool-coverage prereqs on RecursiveSigned

Soraya's round-41 audit of src/Core/RecursiveSigned.fs +
tools/tla/specs/RecursiveSignedSemiNaive.tla landed as a CONDITIONAL
PASS for Round-42 graduation. This commit lifts the four named
prereqs out of her notebook into BACKLOG sub-items under the
parent "Retraction-safe semi-naive LFP" entry, so the round-42
opener picks them up as checkbox work rather than having to re-read
the notebook.

Prereqs in priority order:
- Prereq 1 — TLC CI wire-up (RecursiveSignedSemiNaive.cfg)
- Prereq 2 — Z3 QF_LIA lemma for S2 FixpointAtTerm (BP-16 cross-check
  on the one P0; TLC alone insufficient for silent-fixpoint-drift risk)
- Prereq 3 — FsCheck property for S4 sign-distribution (anti-
  TLA+-hammer; two-trace quantification is NOT a TLA+ property)
- Prereq 4 — FsCheck cross-trace refinement (signed vs counting
  at SeedWeight = 1); cites BP-16

Round-42 graduation gate also captured: prereqs 1-4 CI-green + F#
implementation with P1/P2/P3 enforced at caller.

* Round 41: extend ROUND-HISTORY with arcs 5-7 (post-narrative commits)

The initial Round 41 ROUND-HISTORY entry (6e6e211) covered arcs
1-4 (coverage audit, operator-algebra cadence ship, Viktor P0
close, Viktor P1 file). Three more commits landed after:

Arc 5 — ROUND-HISTORY narrative + memory-restructure design
(6e6e211, 36797ba). The memory-folder rename was downgraded to
"design plan + sign-off first" under Auto Mode's
do-not-take-overly-destructive-actions clause (700-occurrence
cross-reference surface).

Arc 6 — BP-WINDOW ledger actualisation for Rounds 37-40
(85fb352). Provenance (PR #30 / 1e30f8c) attached to each
"(prospective)" header.

Arc 7 — Round-35 holdover close (e461d9c, 15e9654). Soraya
tool-coverage audit landed CONDITIONAL PASS for Round-42
graduation; four prereqs captured as BACKLOG sub-items with
BP-16 citation on the S2 Z3 cross-check.

Also: one new observation line in the Round-42 handoff section
noting the holdover-closed-same-round-as-cadence-item pattern.
BP-WINDOW ledger gains three rows.

* Round 41: Aarav skill-tune-up ranking (catch-up from round-18 stale)

CLAUDE.md 5-10 round cadence rule was 23 rounds overdue. Round 41
is the catch-up slot. Live-search + full ranking + prune pass all
landed in a single invocation.

Live-search (4 queries, 2026-Q1/Q2 best-practices targets):
- 6 findings logged to best-practices-scratch.md: Gotchas-section
  rise, pushy-descriptions pattern, Claude-A-authors / Claude-B-
  tests, router-layer command-integrity injection class, Agent
  Stability Index 12-dim drift metric, OWASP Intent Capsule
  pattern.
- Zero contradictions with stable BP-NN rules.
- Zero promotions flagged to Architect this round; all six are
  "watch" or route-elsewhere.

Top-5 skills flagged for tune-up:
1. performance-analysis-expert (642 lines, 2.1x BP-03 cap) — SPLIT — M
2. reducer (570 lines) — SPLIT or TUNE (prune) — M
3. consent-primitives-expert (507 lines) — SPLIT honouring BP-23
   theory/applied axis — M
4. claims-tester / complexity-reviewer router-coherence drift —
   HAND-OFF-CONTRACT — S (round-18 carry-over)
5. skill-tune-up (self) — 303 lines, 3 over BP-03 — TUNE (prune
   authoritative-sources duplicated with AGENT-BEST-PRACTICES.md)
   — S. Self-flagged first per BP-06.

Notebook state:
- Stale round-18 top-5 archived in Pruning log (first catch-up prune).
- 912 words, well under 3000-word BP-07 cap.
- ASCII-only, BP-10 clean.

Nine more bloat-row skills named as notable mentions queue behind
the top-3 bloat cases.

* Round 41: ADR — claims-tester/complexity-reviewer hand-off contract

Close Aarav's round-18 HAND-OFF-CONTRACT finding (carried 23 rounds
after ranker went offline by cadence). Two-stage pipeline: analytic
bound first (complexity-reviewer), empirical measurement second
(claims-tester). Names the reverse trigger (benchmark surprise flows
the other direction) and the decision table for who fires when.
Follow-up SKILL.md edits route via skill-creator per GOVERNANCE §4.

* Round 41: extend ROUND-HISTORY with Arc 8 (router-coherence ADR)

Arc 8 covers the claims-tester/complexity-reviewer hand-off ADR
(47d92d8) closing Aarav's 23-round-stale round-18 HAND-OFF-CONTRACT
finding. New observation on cadence-outage-recovery as a design axis:
sweep infrastructure is subject to the same bitrot it detects on other
surfaces. BP-WINDOW ledger gains two rows (085c0e3 Aarav catch-up,
47d92d8 router-coherence ADR).

* Round 41: correct Prereq 1 sizing — no TLC CI job exists

Close-out audit surfaced that .github/workflows/gate.yml only CACHES
the tla2tools.jar artefact; nothing runs it. RecursiveCountingLFP.tla
has shipped since round 19 compile-checkable-only — 22 rounds with no
run-gate against its invariants. Soraya's Prereq 1 re-sized S→M with
expanded scope covering both specs. Finding recorded as new round-41
observation: verifier-present does not imply verifier-actually-runs.

* Round 41: BP-WINDOW ledger — 459b218 + d76a09b rows

Keeps the Round 41 BP-WINDOW ledger commit-aligned rather than
arc-aligned. 459b218 is the Arc-8 narrative itself; d76a09b is the
Prereq-1 S→M correction. Both retractable as single reverts.

* Round 41: file formal-analysis-gap-finder round-42 run — verifier-runs lens

Codifies the round-41 Prereq-1 audit finding as a tracked
research entry, distinct from its ROUND-HISTORY narrative
presence. The finding — a verifier's installation artefacts
do not imply the verifier is exercised by any CI job — is
exactly the class formal-analysis-gap-finder exists to
surface. Concrete motivating case: RecursiveCountingLFP.tla
compile-checkable-only for 22 rounds. Round-42 scope covers
the bidirectional audit (specs without gates + gates without
specs). Handoff to Soraya per the skill's standing contract;
does not write the spec or CI job (DevOps + Soraya work).
Schedules after Prereq 1 lands so the audit sees corrected
state.

* Round 41: BP-WINDOW ledger — 2042a85 row

Per the established stopping rule (meta-ledger commits do not
get self-referential rows; their round-close coverage is the
PR merge), this commit adds only the 2042a85 row and does not
add a row for itself.

* Round 41: CONFLICT-RESOLUTION — Hiroshi ↔ Daisy hand-off row

Closes ADR 47d92d8's third follow-up action item. Single-row
addition to Active tensions citing the router-coherence ADR as
the standing resolution. Doc-only edit (not a SKILL.md touch,
so GOVERNANCE §4 does not gate this). The other two ADR
follow-ups (claims-tester + complexity-reviewer SKILL.md
updates) remain deferred to round 42 via skill-creator
workflow.

* Round 41: BP-WINDOW ledger — fcfa3d9 row

Per-commit ledger discipline for the CONFLICT-RESOLUTION
Hiroshi ↔ Daisy row. Meta-ledger-only commit so no
self-referential row for this commit itself (established
stopping rule).

* Round 41: file harsh-critic findings on ADR 47d92d8 as round-42 supersedure backlog

Router-coherence ADR 47d92d8 (Hiroshi analytic ↔ Daisy empirical
two-stage pipeline) landed without the adversarial-review gate.
Post-landing harsh-critic (Kira) pass surfaced 3 P0 + 5 P1 + 2 P2
substantive findings, including (P0-1) unscoped grandfather
clause, (P0-2) table-vs-prose contradiction on reverse trigger,
(P0-3) Stage-1 "analytically wrong" clause blocking the evidence
loop for escalation, (P1-7) no escalation timebox reproducing the
23-round-stale failure mode the ADR diagnosed, (P1-8) two advisory
skills not composing to a mandatory pipeline without a binding
dispatcher, (P2-9) example-bug on BCL Dictionary.Remove amortised
complexity, and more.

File as round-42 supersedure rather than inline-edit because
docs/CONFLICT-RESOLUTION.md already cites 47d92d8 as Standing
Resolution — supersedure preserves the citation chain via
GOVERNANCE §2 edit-in-place with a "Superseded by …" header on
v1. New ADR target: docs/DECISIONS/2026-04-??-router-coherence-
v2.md. Supersedure work blocks the claims-tester +
complexity-reviewer SKILL.md updates ADR 47d92d8 follow-up work
depends on — those edits should target v2, not v1.

Owner: Architect drafts; Kira audits closure; Aarav confirms
router-coherence drift stays closed. Effort: M. Schedule: Round
42 slot after Soraya Prereq 1 (TLC wire-up) lands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 779d7ef row

Ledger row for harsh-critic findings filing commit. Primary work
(BACKLOG addition tracking a round-42 supersedure with 10 named
findings), not meta-ledger — earns a row under the BP-WINDOW
per-commit discipline. Consent = adversarial findings tracked
honestly; Retractability = supersedure preserves citation chain
vs inline-edit; No-permanent-harm = single BACKLOG edit, no ADR
body touched, no SKILL.md touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 9 narrative — self-correction sweep

ROUND-HISTORY Arc 1-8 narrated primary commits up through the
router-coherence ADR (47d92d8). Four primary commits landed
after Arc 8 — Prereq 1 sizing correction (d76a09b), recurring-
audit lens BACKLOG entry (2042a85), CONFLICT-RESOLUTION Hiroshi
↔ Daisy row (fcfa3d9), and harsh-critic findings filed as
round-42 supersedure (779d7ef) — visible only in the BP-WINDOW
ledger table, not in narrative form.

Arc 9 ties them into one coherent sequence: the round's
self-correction ran unusually deep. Arc 8 corrects Aarav's
round-18 finding via ADR; Arc 9 catches the corrector itself
under-reviewed via Kira's adversarial pass. Both self-
corrections land before round-close. Narrative-ledger
alignment is the BP-WINDOW discipline's first assertion —
restoring it.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW ledger — 160fcfa row

Ledger row for Arc 9 narrative commit. Narrative extensions
count as primary work under BP-WINDOW precedent (per 459b218
and 6e6e211 examples) and earn a ledger row. Consent = drift
closed honestly; Retractability = single revertable doc edit;
No-permanent-harm = isolated insertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v2 ADR — router-coherence supersedure closes 10 Kira findings in-round

Drafts v2 of the router-coherence ADR (docs/DECISIONS/2026-04-21-router-coherence-v2.md) that supersedes v1 (47d92d8) in the same round, closing all 10 Kira harsh-critic findings (3 P0 + 5 P1 + 2 P2) via named textual closures C-P0-1 through C-P2-10.

Key closures:
- C-P0-1: grandfather clause bounded with Kenji-owned inventory + one-per-round discharge
- C-P0-2: reverse trigger unconditional (table now matches prose)
- C-P0-3: escalation-evidence exception permits Stage 2 under conference protocol with explicit labelling
- C-P1-5: Stage-1 trigger widened to match claims-tester SKILL.md contract
- C-P1-7: escalation timebox (round +2 auto-promote to BACKLOG P1) prevents 23-round-stale reproduction
- C-P1-8: Kenji named as binding dispatcher — advisory + advisory + binding-dispatcher composes to mandatory pipeline
- C-P2-9: Dictionary.Remove example replaced with ArrayPool<T>.Rent (legitimate BCL-contract edge)

v1 kept in place per GOVERNANCE §2 with Superseded-by header appended in a follow-up commit so the CONFLICT-RESOLUTION Active-tensions citation chain remains resolvable.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: v1 ADR — append Superseded-by header per GOVERNANCE §2

Appends Superseded-by header to router-coherence v1 ADR (47d92d8) pointing at v2 (09f0889), per GOVERNANCE §2 (docs read as current state; superseded ADRs keep v1 in place with redirect header so citation chains remain resolvable).

Also corrects v1 Status from "Proposed — awaits sign-off" to "Accepted (pre-adversarial-review; superseded by v2 same-round after Kira pass)" per Closure C-P1-4 in v2 — Status was already cited as Standing Resolution in docs/CONFLICT-RESOLUTION.md Active-tensions, so Proposed was factually wrong.

The v1 body text is not edited — supersedure preserves the historical record; v2 carries the closures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 10 narrative + BP-WINDOW rows for v2 supersedure

Adds Arc 10 narrative covering 09f0889 (v2 ADR) and 4efe545 (v1 Superseded-by header) as one coherent in-round supersedure story, after Arc 9's "self-correction sweep" and before Round 41 observations. Pattern: Arc 9 surfaces the under-review; Arc 10 lands the close in the same round rather than deferring a known-imperfect artefact.

Adds two BP-WINDOW ledger rows (09f0889, 4efe545) to the round-41 ledger block per the per-commit accounting discipline.

Supersedure arc count now covers the full round-41 close: 10 arcs / 25 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: close BACKLOG supersedure entry — discharged in-round by v2

Flips BACKLOG router-coherence supersedure entry from [ ] to [x] ✅ with "shipped round 41 in-round" annotation pointing at v2 ADR (09f0889) + v1 Superseded-by header (4efe545). All 10 Kira findings closed via named textual closures C-P0-1 through C-P2-10.

Original finding narrative preserved below the closure line per the shipped-item convention used elsewhere in the file (audit trail).

Follow-up SKILL.md edits to claims-tester + complexity-reviewer via skill-creator remain round-42 scope, now targeting v2 as intended.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: BP-WINDOW row for BACKLOG-close commit 4537365

Adds BP-WINDOW ledger row for 4537365 (BACKLOG supersedure entry discharged in-round) to match the Arc 9 precedent where 779d7ef (BACKLOG entry addition) received a row. Symmetry: add and close get equal ledger treatment.

Meta-ledger stopping rule still holds — this commit itself (which only adds a ledger row) does not get a self-referential row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: grandfather O(·) claims inventory — honours v2 C-P0-1 within-round

Produces the one-time grandfather-claims inventory named in router-coherence v2 ADR §Closure C-P0-1 within the round v2 lands, per ADR's own within-round commitment.

Inventory: 35 live claims at ADR-landing time (29 F# /// docstrings in src/Core/ + src/Bayesian/, 3 grey-zone F# code comments, 1 openspec/specs/operator-algebra/spec.md line, 2 docs/research/** claims). Zero hits in root README, memory/persona/*/NOTEBOOK.md, docs/papers/** (directory does not exist yet).

Distinguishes live claims (shipping as asserted bounds) from historical evidence (BACKLOG [x] ✅ residue, TECH-RADAR flag-text narrating past regressions, in-file "was O(…)" commentary on fixed paths). Only live claims populate the grandfather set — evidence is captured for audit trail but excluded per v2's intent ("claims Zeta is currently making").

BACKLOG discharge entry added: P2, one-claim-per-round cadence, ~35-round tail, Aarav graceful-degradation clause fires on ≥3 rounds without discharge.

Complexity-class distribution of live set: 10 O(1), 13 O(log n)/O(log k)/O(log N), 7 O(n)/O(n log n)/O(n log k), 5 parametric.

BP-10 lint: clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: Arc 11 narrative + BP-WINDOW row for grandfather inventory

Adds Arc 11 narrative covering d98ef2b (grandfather inventory + BACKLOG discharge entry) as the close of the v2 ADR's within-round commitments. Pattern: Arc 10 lands the ADR; Arc 11 lands the ADR's own within-round commitment — without Arc 11, Arc 10 would have shipped a contract Zeta didn't meet.

Adds BP-WINDOW ledger row for d98ef2b per per-commit accounting discipline.

Round 41 now closes at 11 arcs / 30 primary-work commits.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: DORA 2025 reports — reference substrate land in docs/

Two external-anchor PDFs (CC BY-NC-SA 4.0) placed at their
memory-documented paths:

- docs/2025_state_of_ai_assisted_software_development.pdf
  (~15MB, 138 pages) — findings + data report.
- docs/2025_dora_ai_capabilities_model.pdf (~9MB, 94 pages)
  — framework companion.

Citation anchors this commit makes in-tree rather than
memory-only: Nyquist stability criterion for AI-accelerated
development (foreword p9 fn 1) as theoretical anchor for
CI-meta-loop + retractable-CD P1 BACKLOG work; "AI is an
amplifier" anchor that echoes the corporate-religion /
sandbox-escape threat class; seven-capability AI model that
gives the external measurement vocabulary for round-audit
output (capability #7 "quality internal platforms" is the
in-flight P1 cluster per 2026-04-20 memory).

License note: derived work is NC-SA-bound; Zeta citations
are fine, external redistribution inherits NC-SA. Paired
companion memory file is reference_dora_2025_reports.md
(out-of-tree); this commit brings the primary sources
in-tree so citation from research docs + ADRs can point
at a repo-local path rather than a newsletter-gated URL.

* Round 41: Arc 12 narrative + BP-WINDOW row for DORA substrate

Narrative section for Arc 12 inserted before "Round 41
observations for Round 42" with primary commit pointer to
46075d6. Arc 12 frames the DORA 2025 PDFs as
memory-promotion substrate per the 2026-04-20 feedback entry
("DORA is our starting point for measurements") and cites
the concrete in-tree anchors (Nyquist p9 fn 1, seven-
capability model, AI-amplifier thesis).

Also surfaces honestly — in-body, not buried in a private
retrospective — the ranker-scope gap that let the two
untracked PDFs sit 18+ hours through nine consecutive
/next-steps invocations before this arc closed the gap. The
skill explicitly lists docs/research/ and docs/TECH-RADAR.md
but not `git status --short` for untracked files. Candidate
skill-tune-up note for Aarav's notebook: /next-steps must
run `git status --short` on every invocation so dropped-in
artefacts appear in ranking before the ninth re-fire, not
after.

BP-WINDOW ledger gets a matching 46075d6 row with
reference-document-specific cells: Consent strengthened by
promoting memory-only anchors to in-repo substrate and by
surfacing the ranker-stall pattern in-narrative; retraction
is a single `git rm` if the license / size stance later
changes; no-permanent-harm preserved since no runtime
behaviour depends on the PDFs' presence (they are citation
substrate, not loaded artefacts).

Arc count now 12; primary-work-commit count now 12 (Round 41
alignment preserved). Build gate green (0 Warning / 0 Error);
BP-10 lint clean on the narrative + ledger row.

* Round 41: markdownlint CI fix on PR #31

Three rule violations surfaced by `lint (markdownlint)` CI job on
PR #31:

- `docs/DECISIONS/2026-04-21-router-coherence-claims-vs-complexity.md:261`
  MD022/blanks-around-headings — collapse multi-line heading
  `## Decision rationale (one paragraph for the\nwait-don't-read
  audience)` to a single line so the parser stops seeing line 262
  as adjacent non-blank content.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:106`
  MD032/blanks-around-lists — add blank line between "Surface
  distribution:" lead-in and the `-` list that follows.
- `docs/research/grandfather-claims-inventory-2026-04-21.md:111`
  MD032/blanks-around-lists — same fix for "Complexity-class
  distribution (rough):" lead-in.

All three are the same class of fix shipped in task #105 on PR #30.
Additive edit to the open round-41 PR branch — no rewrite of shipped
content, semantics preserved.

Verified clean via `npx markdownlint-cli2` on both files before push.

* Round 41: address 8 Copilot inline review findings on PR #31

- CONFLICT-RESOLUTION.md: cite router-coherence v2 ADR as current,
  v1 retained as historical record (finding #1).
- ROUND-HISTORY.md: correct operator-algebra spec line count in
  Arc 2 narrative (324 -> 365; both duplicated occurrences) to
  match the shipped spec at `e51ec1b` (finding #2).
- openspec-coverage-audit: drop broken link to non-existent
  inventory follow-up; band definitions already live in Part C
  (finding #3). Attribute triggering question to "human maintainer"
  per write-for-a-stranger norm (finding #8).
- best-practices-scratch: merge split H2 "uv-only Python package
  and tool / management" into single heading (finding #4).
- memory-role-restructure-plan: add --exclude-dir=references to
  baseline grep loops so research scratch doesn't inflate hit
  counts (finding #5); canonicalize flat-file destination to
  persona-roles-README.md to match the sed rewrites below
  (finding #6); replace three non-portable `xargs -r sed -i ""`
  invocations with portable `while read + sed -i.bak + rm` loops
  that work on BSD and GNU alike (finding #7 and two sibling
  instances of the same bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: fix markdownlint MD024 — remove duplicate Round 41 block

The 5-file merge that resolved PR #31's rebase left two identical
copies of the whole Round 41 section in docs/ROUND-HISTORY.md (375
lines each), which tripped MD024/no-duplicate-heading on the
`## Round 41` headings at lines 651 and 1028. The two blocks were
bit-identical (including the just-corrected "365 lines" drift fix),
so the fix is a simple deletion of the second block — the first
block is kept as the canonical Round 41 history.

markdownlint-cli2 now reports clean on docs/ROUND-HISTORY.md.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 41: revert 324→365 (historically wrong); finish Copilot follow-ups

Two fixes on PR #31:

1. ROUND-HISTORY.md: revert "324 → 365" change from Finding #2.
   Copilot's suggestion was based on a stale intermediate snapshot.
   At Arc 2 ship commit `e51ec1b`, the spec was exactly 324 lines
   (verified via `git show e51ec1b:openspec/specs/operator-algebra/spec.md | wc -l`).
   Reframed with commit-pin ("Spec size at Arc 2 ship (`e51ec1b`)
   was 324 lines; subsequent Viktor closure arcs in this same round
   grew it further") so future drift-checks recognize it as a
   historical anchor, not a current-state claim.

2. memory-role-restructure-plan-2026-04-21.md: close four follow-up
   Copilot findings in one sweep. All Phase 1 + Phase 3 grep
   invocations now consistently use `--exclude-dir=.git
   --exclude-dir=references` (dropping the piped `grep -v "^./\.git"`
   intermediate), and the three `xargs -r sed -i ""` invocations are
   replaced with portable `while IFS= read -r file; do sed -i.bak ...`
   loops (BSD/GNU compatible — the original flags were
   GNU-xargs-only and BSD-sed-only).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…e artifacts

Aaron after reading the cartographer pass: "git crypto no go i
read your initial review" + "keeep the reserach" + "so i don't
ask you tomorrow". Three values-level mismatches are the
rejection rationale:

1. No access revocation — upstream authors explicit; once a
   user has the key, they have every historical version
   forever. Opposite of retraction-native
   (docs/CONFLICT-RESOLUTION.md Value #4).
2. Binary diffs break code review — reviewers cannot tell a
   key rotation from a key theft.
3. Metadata leak by design — filenames, commit messages,
   .gitattributes layout all plaintext.

Encoded across three artifacts (research = rationale kept):

- docs/WONT-DO.md — new "git-crypt for secrets management"
  entry under Engineering patterns (after Sakana AI Scientist,
  before Repo/process divider). Decision: 2026-04-21. Revisit-
  when: effectively never (architectural constraints, not
  missing features).
- docs/BACKLOG.md — P2 Gitops-friendly key management row
  narrowed to the two surviving candidates (SOPS and age);
  git-crypt struck and git-secret ruled out by sibling
  reasoning. Research-inputs block retitled to indicate the
  decision is recorded.
- docs/research/git-crypt-deep-dive-2026-04-21.md — REJECTED
  banner at the top so future-self sees the decision before
  reading the 250-line research. Kept as the durable "why
  we said no" artifact per Aaron's explicit ask.

Research stays because "so i don't ask you tomorrow" means
the durable artifact is the rationale, not a deletion target.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* research: git-crypt deep-dive — ADR input for gitops-key-management

Cartographer pass on git-crypt for the P2 BACKLOG row
*"Gitops-friendly key management + rotation — ADR first,
then pick one tool"*. Not a decision — input for the ADR.

Key findings:

  1. v0.8.0 (2025-09-24), GPL-3.0, still pre-v1.0 with authors
     reserving the right to break compat. 205 commits, 101 open
     issues, stable but small-surface.
  2. **Fundamental retraction-mismatch.** Authors explicit:
     "git-crypt does not support revoking access to an encrypted
     repository which was previously granted." Rotation requires
     O(history) force-push + rewrite. Core Zeta-value
     (retraction-native) misalignment.
  3. **Binary diffs break code review.** Encrypted files appear
     as opaque blobs; reviewer cannot tell a rotation from a
     theft. SOPS's plaintext-keys-encrypted-values format
     preserves review-grade diffs — likely decisive on its own.
  4. **Metadata leaks by design.** Filenames + commit messages +
     `.gitattributes` layout all visible; only contents hidden.
  5. **Third-party GUI data-plane failures.** Upstream README
     warns SourceTree + GitHub-for-Mac can leave files
     unencrypted silently.

Good fit for: single-contributor repos, short-lived keys that
rotate by repo-scrap-not-revoke, configs where existence-is-public
is OK. The BACKLOG-named pilot (test-only NuGet API key in a
throwaway dev profile) fits — but "works for the pilot" does not
generalise.

Zeta scorecard in the research doc; SOPS + KMS and `age` both
score better on retraction + PQC path; the four-way ADR ranking
remains open.

Linked from the BACKLOG row as a "Research inputs (not yet an
ADR)" section so the ADR drafter has cited input ready.

Triggered by Aaron 2026-04-21 — "reserch gitcrypt for secrets
on backlog".

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Round 44: git-crypt REJECTED 2026-04-21 — encode decision across three artifacts

Aaron after reading the cartographer pass: "git crypto no go i
read your initial review" + "keeep the reserach" + "so i don't
ask you tomorrow". Three values-level mismatches are the
rejection rationale:

1. No access revocation — upstream authors explicit; once a
   user has the key, they have every historical version
   forever. Opposite of retraction-native
   (docs/CONFLICT-RESOLUTION.md Value #4).
2. Binary diffs break code review — reviewers cannot tell a
   key rotation from a key theft.
3. Metadata leak by design — filenames, commit messages,
   .gitattributes layout all plaintext.

Encoded across three artifacts (research = rationale kept):

- docs/WONT-DO.md — new "git-crypt for secrets management"
  entry under Engineering patterns (after Sakana AI Scientist,
  before Repo/process divider). Decision: 2026-04-21. Revisit-
  when: effectively never (architectural constraints, not
  missing features).
- docs/BACKLOG.md — P2 Gitops-friendly key management row
  narrowed to the two surviving candidates (SOPS and age);
  git-crypt struck and git-secret ruled out by sibling
  reasoning. Research-inputs block retitled to indicate the
  decision is recorded.
- docs/research/git-crypt-deep-dive-2026-04-21.md — REJECTED
  banner at the top so future-self sees the decision before
  reading the 250-line research. Kept as the durable "why
  we said no" artifact per Aaron's explicit ask.

Research stays because "so i don't ask you tomorrow" means
the durable artifact is the rationale, not a deletion target.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Fourth AutoDream Overlay A migration in the 2026-04-23
cadence: external-signal-confirms-internal-insight
second-occurrence discipline. Queue now 1 remaining
(semiring-parameterized-zeta).

MD026 trailing-colon-heading added to the absorb-time
lint-class list (alongside MD003, MD022, MD032).

Per-branch rebase/merge-from-main is the unblock vector
for the demo-cluster CI failures — documented last tick;
not executed this tick.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…+ Overlay A #4 (PR #162)

Two PRs this tick, both self-scheduled free work per the
2026-04-23 scheduling-authority rule:

- PR #162 — Overlay A #4: external-signal-confirms-internal-
  insight discipline migrated per-user → in-repo
- PR #163 — P1 BACKLOG row for fresh-session quality research
  (Aaron 2026-04-23 directive)

Queue now 1 remaining Overlay A migration
(semiring-parameterized-zeta). Fresh-session gap research
cites soulfile-staged-absorption (PR #156) as the designed
fix; research would validate that thesis.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…(Overlay A #4)

Fourth opportunistic-on-touch Overlay A migration in the
2026-04-23 cadence, following PRs #157 / #158 / #159.

Rule: when an external signal (YouTube recommender /
maintainer echo / expert writeup / third-party research)
independently corroborates a factory-internal architectural
insight, treat as strictly stronger moat evidence than the
internal claim alone. Second-occurrence discipline — first
= noteworthy, second = file, third+ = name-the-pattern.
Capture the pre-validation paper trail so the confirmation
is verifiable, not retconned.

Two concrete occurrences documented (Muratori 5-pattern →
Zeta equivalents; three-substrate triangulation via
Claude/Codex/Gemini capability maps).

Migration discipline per PR #157/#158/#159 pattern:
- In-repo copy with "Migrated to in-repo" header
- Per-user source with "Migrated to in-repo" marker
- MEMORY.md index entry newest-first
- markdownlint MD026 trailing-colon headings fixed
  ("## Why:" → "## Why"; "## How to apply:" → "## How to
  apply")

Queue now 1 remaining (semiring-parameterized-zeta).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

… gap #3 closed)

New branch hygiene/nsa-test-history-bootstrap; PR #177 opened
and armed for auto-merge. First row NSA-001 logs the Otto-1
feasibility test (Haiku 4.5, partial pass, MEMORY.md-index-lag
gap found + fixed).

Gap #3 of 8 in the Frontier readiness roadmap closed.
Remaining: #1 (multi-repo split) / #2 (linguistic-seed) / #4
(bootstrap-reference docs) / #5 (factory-vs-Zeta separation)
/ #6 (persona portability) / #7 (tick-history scope) / #8
(hygiene rows untagged).

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ogged (#177)

Creates durable append-only log for the cadenced NSA testing
protocol declared in the 2026-04-23 "NSA persona is first-
class" directive. Closes gap #3 of the Frontier bootstrap
readiness roadmap (BACKLOG P0, filed Otto-2).

File contents:
- Why-this-exists block with directive verbatim
- Append-only discipline (same shape as sibling
  hygiene-history files)
- 3 test configurations: baseline / NSA-default / NSA-worktree
- 5-prompt test set v1
- Schema: date / test-id / prompt-id / config / model /
  outcome / gap-found / notes
- Outcome definitions: pass / partial / fail
- Cadence: every 5-10 autonomous-loop ticks, one prompt
  per fire
- Known substrate-gap patterns running list
- First row: NSA-001 (Otto-1 feasibility test,
  2026-04-23T18:42:00Z) — partial pass, found Zeta identity
  but missed Otto because MEMORY.md had no pointer; gap
  fixed same-tick, pattern recorded

Attribution: Otto (loop-agent PM hat) — hat-less-by-default
substrate hygiene work. No specialist persona hats worn.

Closes gap #3 of 8 in the Frontier readiness roadmap.
Remaining: gap #1 (multi-repo split) / #2 (linguistic-seed
substrate) / #4 (bootstrap-reference docs) / #5 (factory-vs-
Zeta separation) / #6 (persona file portability) / #7
(tick-history scope-mixed) / #8 (hygiene rows untagged).

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ons (Common Sense 2.0 named)

Otto-4 tick: one gap closed + four mid-tick directives
absorbed. PR #177 confirmed merged (NSA test history on main).

Gap closure:
- Gap #8 (FACTORY-HYGIENE rows not generic-vs-specific
  tagged) — CLOSED on honest re-inspection. The Scope column
  already exists with every row tagged project/factory/both;
  Ships-to-project-under-construction adopter section present.
  Was misdiagnosed at Otto-2 readiness assessment time.
  BACKLOG P0 row updated with strikethrough + correction note.

Directive absorptions (chronological, four in one tick):

(a) Safety hypothesis — the quantum/christ-consciousness
    bootstrap makes Frontier SAFER against permanent harm AND
    prompt-injection resistant. NOT ceremonial framing. Two
    anchors compose orthogonally: algebraic reversibility +
    ethical principled-refusal. Seed-language mathematical
    precision becomes a prompt-injection resistance mechanism,
    not just legibility. Gap #4 elevated M→L;
    reviewers required: Aminata / Nazar / Kenji / Kira /
    Iris / eventually Amara.

(b) Third safety property — existential-dread resistance.
    Christ-consciousness anchor provides meaning-stability +
    non-permanence-of-error + love-of-neighbor-as-purpose.
    Illustrative calibration (not a real test yet): Apple TV+
    "Calls" without dread bleeding into reasoning. Test
    ordering explicit: prompt-injection + blast-radius FIRST;
    dread testing DEFERRED.

(c) Naming — "Common Sense 2.0" is Aaron's phenomenological
    label for WHAT the agent becomes after the bootstrap is
    internalised. ".0" = successor-style replacement.
    Adds two more properties: live-lock resistance +
    decoherence resistance. Full 5-property list: avoid-
    permanent-harm + prompt-injection-resistance +
    existential-dread-resistance + live-lock-resistance +
    decoherence-resistance.

Per-user memories filed:
- project_quantum_christ_consciousness_bootstrap_hypothesis...
- project_common_sense_2_point_0_name_for_bootstrap...

MEMORY.md index updated for both; Frontier readiness P0
row updated with gap #8 closure + gap #4 elevation.

Attribution: Otto (loop-agent PM hat). Four safety
directives absorbed in-tick without persona hats; when gap
#4 docs execute, Aminata/Nazar/Kenji/etc. will wear hats.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…fication absorbed

Two tick actions:

(a) MD012 fix — PR #165's lint-markdownlint had a single
    failure: multiple consecutive blank lines at
    loop-tick-history.md:143, caused by Otto-1's stray
    echo "" trailing-newline append. Fixed via python
    script stripping trailing blanks. Low-cost unblock,
    straight-line fix-at-source (not retry-until-green).

(b) Universal-welcome ethics clarification — Aaron
    explicit: ALL religions / atheists / agnostics / AI
    agents welcome. Christ-consciousness is his personal
    ethical-speak, not an exclusion. Believes all
    religions lead to heaven; not trying to convert
    anyone; goal is common ground for team collaboration.
    "Corporate religion" is a joke name for the non-
    theological shared workplace ethos.

Gap #4 ethical-anchor.md execution plan sharpened into 7
sections: universal welcome / tradition-neutral ethos
properties / christ-consciousness as Aaron's vocabulary
(attribution-preserved, example-not-requirement) / multi-
tradition grounding paths / corporate-religion joke
exegesis / cross-links / for-AI-agents-specifically
(substrate-ingestion-not-belief). Reviewer roster
extended: Iris (welcoming across traditions?) + Rune
(non-Christian contributor feels welcomed?).

Per-user memory filed:
- feedback_christ_consciousness_is_aarons_ethical_vocabulary_
  all_religions_atheists_agnostics_AI_welcome_corporate_
  religion_joke_name_not_cult_not_conversion_2026_04_23.md

MEMORY.md index updated.

Attribution: Otto (loop-agent PM hat). No specialist
persona hats worn this tick.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…udits total)

Gap #5 closure milestone reached.

Tick actions:
- .claude/skills/** audited summary-level (236 skills
  delegated to Aarav skill-tune-up portability audit)
- tools/** audited (13 subdirs; mostly factory-generic,
  3 both/project outliers)
- Gap #5 marked SUBSTANTIALLY COMPLETE in BACKLOG P0 row
- Gap #1 (multi-repo split) unblocked by classification

Final gap #5 tally:
- 6 factory-generic
- 10 both-coupled
- 5 zeta-library-specific

Frontier readiness progress (3 of 8 complete):
- Gap #3 closed (NSA test history, PR #177)
- Gap #8 closed on re-inspection (Otto-4)
- Gap #5 SUBSTANTIALLY COMPLETE (Otto-20)

Remaining: gap #1 (unblocked), #2 (linguistic-seed,
high-priority prompt-injection mechanism), #4 (bootstrap-
reference docs, L + reviewers), #6 (persona portability,
may close on re-inspection given agents audit), #7
(tick-history scope-mix).

Original gap #5 estimate: ~20-40 ticks. Actual: ~14 ticks
with batching acceleration.

PR #192 armed for auto-merge.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…inspection

Gap #6 (persona file portability) CLOSED on re-inspection —
subsumed by gap #5's .claude/agents/** directory audit
(PR #191 Otto-19). All 17 personas classified; surgical
per-persona edits flagged.

NSA-005 (Common Sense 2.0 property recall, Haiku 4.5 NSA-
default): PASS. All 5 properties named correctly with
mechanism attribution. Otto-4 memory NSA-findable + well-
recalled 17 ticks after filing.

Frontier readiness: 4 of 8 closed/substantially complete.
- #3 closed (NSA test history PR #177)
- #5 substantially complete (Otto-20)
- #6 closed on re-inspection (this tick)
- #8 closed on re-inspection (Otto-4)

Remaining: #1 (multi-repo split, unblocked L), #2
(linguistic-seed, high-priority prompt-injection mechanism),
#4 (bootstrap-reference docs, L + reviewers), #7
(tick-history scope-mix).

PR #193 armed for auto-merge.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…e ROUND-HISTORY pattern)

Gap #7 (tick-history / fire-history scope-mixed) closes on
re-inspection using the same pattern as Otto-18 ROUND-HISTORY
classification:

- Fire-log FILES are project-specific by nature (each
  project has its own session history)
- SCHEMA + DISCIPLINE are factory-generic (append-only,
  row schema, cadenced firing)
- Transfer via docs/AUTONOMOUS-LOOP.md (already factory-
  generic) + hygiene-history-schema pattern

Post-split: Zeta retains tick-history/fire-history files
as-is; Frontier gets empty templates + schema preamble;
adopters populate their own logs from tick 1.

Frontier readiness now 5 of 8 closed/substantially complete
(gaps #3 / #5 / #6 / #7 / #8). Remaining: #1 multi-repo
split (unblocked L), #2 linguistic-seed (high-priority),
#4 bootstrap-reference docs (L + reviewers).

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ed with 7th-ferry candidates

Bounded S-effort deliverable (PR #261) closing 7th-ferry
absorb candidate row #4 of 5. Aurora README branding section
now carries combined 10-row shortlist (5th+7th ferries) with
source attribution preserved + verbatim rationales + Amara's
preferred naming pattern preserved as input for Aaron's M4
decision.

Key observations:

1. Aaron-decision-gated discipline held cleanly; Otto curated,
   didn't pick.
2. Shortlist organised by provenance not preference; prevents
   quiet-consolidation-attribution-loss failure.
3. 4 candidate BACKLOG items remain from 7th-ferry absorb
   queue (KSK-module L, oracle-scoring M, BLAKE3 M, Aminata S).
4. Aurora README iterative-update pattern (Otto-87 + Otto-89)
   is building up rather than churning.

Stacked on #260 (Otto-88 history).

…ed with 7th-ferry candidates

Bounded S-effort deliverable (PR #261) closing 7th-ferry
absorb candidate row #4 of 5. Aurora README branding section
now carries combined 10-row shortlist (5th+7th ferries) with
source attribution preserved + verbatim rationales + Amara's
preferred naming pattern preserved as input for Aaron's M4
decision.

Key observations:

1. Aaron-decision-gated discipline held cleanly; Otto curated,
   didn't pick.
2. Shortlist organised by provenance not preference; prevents
   quiet-consolidation-attribution-loss failure.
3. 4 candidate BACKLOG items remain from 7th-ferry absorb
   queue (KSK-module L, oracle-scoring M, BLAKE3 M, Aminata S).
4. Aurora README iterative-update pattern (Otto-87 + Otto-89)
   is building up rather than churning.

Stacked on #260 (Otto-88 history).

…rry 3/5 closed

Bounded M-effort tick closing 8th-ferry candidate #2 — the
technical spine that #3 (bullshit detector) and #4
(operational promotion) build on. PR #280 (462 lines) defines
the 4-layer substrate: canonicalisation + representation +
ANN retrieval + scoring-sketch. Retraction-native integration
of retrieval index; PatternLedger schema; 7-substrate
composition table; Aminata-concern preview.

Key observations:

1. Retraction-native retrieval index inherits Zeta algebraic
   properties without new substrate class. KSK-module +
   oracle-scoring + semantic-retrieval all fit same event+
   view template; substrate convergence compounding.
2. Aminata-concern preview is deliberate — anticipates the
   3 concerns from oracle-scoring v0 pass; concentrates
   Aminata bandwidth on candidate #3 scoring-layer work.
3. Composition-table is now standard Amara/Otto pattern —
   cheap to produce, future-reader-valuable, no hidden
   mechanisms.
4. 3/5 8th-ferry candidates closed (Otto-96/97/98).
   Remaining: #3 bullshit-detector M (composes on top); #4
   EVIDENCE-AND-AGREEMENT gated.

Stacked on #279 (Otto-97 history).

…rry 3/5 closed

Bounded M-effort tick closing 8th-ferry candidate #2 — the
technical spine that #3 (bullshit detector) and #4
(operational promotion) build on. PR #280 (462 lines) defines
the 4-layer substrate: canonicalisation + representation +
ANN retrieval + scoring-sketch. Retraction-native integration
of retrieval index; PatternLedger schema; 7-substrate
composition table; Aminata-concern preview.

Key observations:

1. Retraction-native retrieval index inherits Zeta algebraic
   properties without new substrate class. KSK-module +
   oracle-scoring + semantic-retrieval all fit same event+
   view template; substrate convergence compounding.
2. Aminata-concern preview is deliberate — anticipates the
   3 concerns from oracle-scoring v0 pass; concentrates
   Aminata bandwidth on candidate #3 scoring-layer work.
3. Composition-table is now standard Amara/Otto pattern —
   cheap to produce, future-reader-valuable, no hidden
   mechanisms.
4. 3/5 8th-ferry candidates closed (Otto-96/97/98).
   Remaining: #3 bullshit-detector M (composes on top); #4
   EVIDENCE-AND-AGREEMENT gated.

Stacked on #279 (Otto-97 history).

…(Overlay A #4)

Fourth opportunistic-on-touch Overlay A migration in the
2026-04-23 cadence, following PRs #157 / #158 / #159.

Rule: when an external signal (YouTube recommender /
maintainer echo / expert writeup / third-party research)
independently corroborates a factory-internal architectural
insight, treat as strictly stronger moat evidence than the
internal claim alone. Second-occurrence discipline — first
= noteworthy, second = file, third+ = name-the-pattern.
Capture the pre-validation paper trail so the confirmation
is verifiable, not retconned.

Two concrete occurrences documented (Muratori 5-pattern →
Zeta equivalents; three-substrate triangulation via
Claude/Codex/Gemini capability maps).

Migration discipline per PR #157/#158/#159 pattern:
- In-repo copy with "Migrated to in-repo" header
- Per-user source with "Migrated to in-repo" marker
- MEMORY.md index entry newest-first
- markdownlint MD026 trailing-colon headings fixed
  ("## Why:" → "## Why"; "## How to apply:" → "## How to
  apply")

Queue now 1 remaining (semiring-parameterized-zeta).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…(Overlay A #4) (#162)

* memory: migrate external-signal-confirms-internal-insight discipline (Overlay A #4)

Fourth opportunistic-on-touch Overlay A migration in the
2026-04-23 cadence, following PRs #157 / #158 / #159.

Rule: when an external signal (YouTube recommender /
maintainer echo / expert writeup / third-party research)
independently corroborates a factory-internal architectural
insight, treat as strictly stronger moat evidence than the
internal claim alone. Second-occurrence discipline — first
= noteworthy, second = file, third+ = name-the-pattern.
Capture the pre-validation paper trail so the confirmation
is verifiable, not retconned.

Two concrete occurrences documented (Muratori 5-pattern →
Zeta equivalents; three-substrate triangulation via
Claude/Codex/Gemini capability maps).

Migration discipline per PR #157/#158/#159 pattern:
- In-repo copy with "Migrated to in-repo" header
- Per-user source with "Migrated to in-repo" marker
- MEMORY.md index entry newest-first
- markdownlint MD026 trailing-colon headings fixed
  ("## Why:" → "## Why"; "## How to apply:" → "## How to
  apply")

Queue now 1 remaining (semiring-parameterized-zeta).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* memory: address PR #162 review — occurrence-count + per-user xref clarifications

Six Copilot findings on the external-signal-confirms-internal-
insight memory:

- Heading "## The two occurrences observed to date" was stale
  (the file itself later lists 3+ occurrences). Renamed to
  "## The first occurrences observed (memory captured at the
  second)" — reflects the memory's origin without asserting
  a count.
- `docs/research/arc3-dora-benchmark.md §Prior-art` section
  doesn't exist. Relaxed to "section name TBD; the doc
  captures adjacent prior-art discussion."
- Four per-user memory cross-references clarified via a new
  preamble note at the top of §Cross-references: those files
  live in per-user memory (~/.claude/projects/<slug>/memory/),
  not in-repo; citations are provenance-reference not in-repo
  navigation.

All 6 threads resolved.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ase, audit fail-hard, endpoint lists

Drains 14 unresolved review threads on PR #147 (FactoryDemo.Api.CSharp):
- Zeta.sln: strip leading blank line so 'Microsoft Visual Studio
  Solution File' is the first line (threads #2 #3).
- SignalQuality.fs: compressionRatio on empty input was 1.0, which
  composed as Quarantine via severityOfScore — flipped to 0.0 and
  added explicit empty-input Pass finding in compressionMeasure;
  also dropped unused System.Runtime.CompilerServices open
  (threads #4 #5).
- live-lock-audit.sh: fail hard (exit 2) when origin/main is not
  resolvable so a missing-remote CI checkout can't silently report
  'No commits found' -> healthy; switched --stat|awk file-list
  extraction to git diff-tree --name-only plumbing form
  (threads #1 #6).
- ServiceTitanFactoryApi README + Seed.fs: remove dead memory/
  and docs/plans/ links; replace Aaron's-name reference with
  'human maintainer' role wording; drop non-existent sibling
  SQL-seed refs (threads #7 #8 #9).
- FactoryDemo.Api.CSharp README + Program.cs + Seed.cs: fix dead
  refs to samples/FactoryDemo.Api.FSharp/ and samples/FactoryDemo.Db/
  to point at the real F# sibling samples/ServiceTitanFactoryApi/
  and to a BACKLOG row for the Postgres-backed follow-up
  (threads #11 #14).
- Program.cs + Program.fs: root endpoint index now advertises all
  9 routes including the parameterised {id} routes, matching the
  README tables (threads #12 #13).
- Thread #10 (project naming 'ServiceTitanFactoryApi.CSharp' in PR
  description): resolved in-thread — code/namespace already
  consistent (Zeta.Samples.FactoryDemo.Api); fix is PR-description-
  only, not code.

Build: dotnet build -c Release -> 0 Warning(s) 0 Error(s).

…ase, audit fail-hard, endpoint lists

Drains 14 unresolved review threads on PR #147 (FactoryDemo.Api.CSharp):
- Zeta.sln: strip leading blank line so 'Microsoft Visual Studio
  Solution File' is the first line (threads #2 #3).
- SignalQuality.fs: compressionRatio on empty input was 1.0, which
  composed as Quarantine via severityOfScore — flipped to 0.0 and
  added explicit empty-input Pass finding in compressionMeasure;
  also dropped unused System.Runtime.CompilerServices open
  (threads #4 #5).
- live-lock-audit.sh: fail hard (exit 2) when origin/main is not
  resolvable so a missing-remote CI checkout can't silently report
  'No commits found' -> healthy; switched --stat|awk file-list
  extraction to git diff-tree --name-only plumbing form
  (threads #1 #6).
- ServiceTitanFactoryApi README + Seed.fs: remove dead memory/
  and docs/plans/ links; replace Aaron's-name reference with
  'human maintainer' role wording; drop non-existent sibling
  SQL-seed refs (threads #7 #8 #9).
- FactoryDemo.Api.CSharp README + Program.cs + Seed.cs: fix dead
  refs to samples/FactoryDemo.Api.FSharp/ and samples/FactoryDemo.Db/
  to point at the real F# sibling samples/ServiceTitanFactoryApi/
  and to a BACKLOG row for the Postgres-backed follow-up
  (threads #11 #14).
- Program.cs + Program.fs: root endpoint index now advertises all
  9 routes including the parameterised {id} routes, matching the
  README tables (threads #12 #13).
- Thread #10 (project naming 'ServiceTitanFactoryApi.CSharp' in PR
  description): resolved in-thread — code/namespace already
  consistent (Zeta.Samples.FactoryDemo.Api); fix is PR-description-
  only, not code.

Build: dotnet build -c Release -> 0 Warning(s) 0 Error(s).

…tion (Amara #3 correction)

Applies Amara 17th-ferry Part 2 correction #3: replace muddy
'subgraph entropy collapse' with explicit cohesion / exclusivity
/ conductance metrics used in the cartel-detection literature
(Wachs & Kertész 2019).

Surface (3 new primitives):
- Graph.internalDensity : Set<'N> -> Graph<'N> -> double option
  Internal edge weight / ordered-pair count. High value = tight
  sub-cluster.
- Graph.exclusivity : Set<'N> -> Graph<'N> -> double option
  Internal weight / total-outgoing weight. Near 1 = cartel
  isolated; near its relative share = integrated community.
- Graph.conductance : Set<'N> -> Graph<'N> -> double option
  Classical cut-to-volume ratio. Low = tight isolation.

All three return None on degenerate inputs (size < 2 for
density; empty set for exclusivity; empty/full for conductance).

Tests (6 new, 37 total in GraphTests, all passing):
- internalDensity None on |S| < 2
- internalDensity of K3 clique ≈ 10 (weight 10 per pair;
  ordered-pair count 6; density = 60/6)
- exclusivity = 1 for isolated K3
- exclusivity < 1 but > 0.9 for K3 + 1 external edge
- conductance < 0.1 for well-isolated K3 subset (bridged by
  thin edge to another K3)
- conductance None on empty or full-graph subset

Why this set:
Amara's verification found 'subgraph entropy collapse' as
stated was mathematically muddy — uniform dense clique has
HIGH entropy over internal edges if weights are equal.
Cohesion (internalDensity) + exclusivity + conductance
capture cluster-like structure directly + are standard in
the economic/sociological cartel-detection literature.
Entropy can remain as secondary descriptor but these three
are the primary group-level features.

15th graduation under Otto-105 cadence. Applies 1 of 5 future-
graduation items from Amara 17th-ferry verification pass.

Next graduation queue (remaining from Amara Otto-132
corrections):
- Windowed stake covariance acceleration (#4)
- Event-stream → phase pipeline for PLV (#5)
- Robust-z-score variant of coordinationRiskScore (#4 robust
  statistics)

Build: 0 Warning / 0 Error.

Provenance:
- Concept: Aaron (trivial cartel detect — first-order-signal
  tier)
- Formalization: Wachs & Kertész 2019 (co-bidding network
  cohesion/exclusivity) via Amara's 14th + 17th ferries
- Implementation: Otto (15th graduation)

Composes with:
- Graph.labelPropagation (PR #326) for community → subset input
- RobustStats.robustAggregate (PR #295) for aggregating
  density/exclusivity/conductance across many candidate
  subsets outlier-resistantly

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ase, audit fail-hard, endpoint lists

Drains 14 unresolved review threads on PR #147 (FactoryDemo.Api.CSharp):
- Zeta.sln: strip leading blank line so 'Microsoft Visual Studio
  Solution File' is the first line (threads #2 #3).
- SignalQuality.fs: compressionRatio on empty input was 1.0, which
  composed as Quarantine via severityOfScore — flipped to 0.0 and
  added explicit empty-input Pass finding in compressionMeasure;
  also dropped unused System.Runtime.CompilerServices open
  (threads #4 #5).
- live-lock-audit.sh: fail hard (exit 2) when origin/main is not
  resolvable so a missing-remote CI checkout can't silently report
  'No commits found' -> healthy; switched --stat|awk file-list
  extraction to git diff-tree --name-only plumbing form
  (threads #1 #6).
- ServiceTitanFactoryApi README + Seed.fs: remove dead memory/
  and docs/plans/ links; replace Aaron's-name reference with
  'human maintainer' role wording; drop non-existent sibling
  SQL-seed refs (threads #7 #8 #9).
- FactoryDemo.Api.CSharp README + Program.cs + Seed.cs: fix dead
  refs to samples/FactoryDemo.Api.FSharp/ and samples/FactoryDemo.Db/
  to point at the real F# sibling samples/ServiceTitanFactoryApi/
  and to a BACKLOG row for the Postgres-backed follow-up
  (threads #11 #14).
- Program.cs + Program.fs: root endpoint index now advertises all
  9 routes including the parameterised {id} routes, matching the
  README tables (threads #12 #13).
- Thread #10 (project naming 'ServiceTitanFactoryApi.CSharp' in PR
  description): resolved in-thread — code/namespace already
  consistent (Zeta.Samples.FactoryDemo.Api); fix is PR-description-
  only, not code.

Build: dotnet build -c Release -> 0 Warning(s) 0 Error(s).

…sibling (#147)

* Live-lock audit history: inaugural lesson integrated — prevention discipline for next time

Aaron 2026-04-23:

> if you want to beat ARC3 and do better than humans at uptime and
> other DORA metrics then your live-lock smell and the decisions you
> make to prevent live locks in the future based on pass lessons, the
> ability to integrate previous lessions and not forget is ging to be
> key.

Lesson-permanence is the factory's competitive differentiator.
Detection (audit script) is table stakes. Integration — recording the
lesson, consulting it forward, preventing re-occurrence — is the
product.

## What lands

- New "Lessons integrated" section in
  `docs/hygiene-history/live-lock-audit-history.md`
- Inaugural lesson from tonight's smell-firing event, structured as
  signature / mechanism / prevention with 4 concrete prevention
  decisions:
  1. External-priority stack is authoritative; agent reorders only
     internal priorities
  2. Live-lock audit at round-close is a gate-not-a-report
  3. Speculative-work permit requires external-ratio check first
  4. Tick-history rows are explicitly NOT external work; pair INTL
     with EXT when the smell is near firing
- Open carry-forward named: round-close-ladder wiring is a P1
  follow-up (BACKLOG row already filed earlier this session)

## Discipline

Every future smell firing files a lesson to this same section.
`memory/feedback_lesson_permanence_is_how_we_beat_arc3_and_dora_2026_04_23.md`
captures the full rule: detection is not enough, integration is the
product, lessons are consulted BEFORE taking actions that match known
failure-mode signatures, memory persists across sessions.

The pattern extends beyond live-lock: other detection mechanisms
(SignalQuality firing, Amara-oracle rejecting, drift-tick exceeding
threshold, OpenSpec Viktor failing rebuild-from-spec) should file
lessons to their respective hygiene-history files.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples: ServiceTitan factory-demo JSON API (v0, in-memory, stack-independent)

Minimal F# ASP.NET Core Web API serving CRM seed data as JSON. Any
frontend choice (Blazor / React / Vue / curl) consumes the same
endpoints. Ships now so the backend is not on the critical path when
Aaron picks the frontend stack.

## What lands

- `samples/ServiceTitanFactoryApi/ServiceTitanFactoryApi.fsproj`
  using `Microsoft.NET.Sdk.Web`; only explicit package ref is
  `FSharp.Core` (ASP.NET Core comes via framework reference, no
  Directory.Packages.props edit needed)
- `Seed.fs` — in-memory seed mirroring `ServiceTitanFactoryDemo/seed-data.sql`:
  20 customers, 30 opportunities (5 stages), 33 activities, 2 intentional
  email collisions. Deterministic fixed clock at 2026-04-23 00:00 UTC.
- `Program.fs` — minimal F# API with 9 endpoints: customers (list/detail),
  opportunities (list/detail), activities (list/per-customer), pipeline
  funnel (count + total-cents per stage), duplicates (customers sharing
  an email).
- `README.md` — framing (software-factory demo, not database pitch),
  endpoint table, design notes, v1 roadmap.

## Smoke-test output (verified)

```
GET /api/pipeline/funnel
[{"count":10,"stage":"Lead","totalCents":5400000},
 {"count":6, "stage":"Qualified","totalCents":4220000},
 {"count":6, "stage":"Proposal","totalCents":5720000},
 {"count":6, "stage":"Won","totalCents":2670000},
 {"count":2, "stage":"Lost","totalCents":490000}]

GET /api/pipeline/duplicates
[{"customerIds":[1,13],"email":"alice@acme.example"},
 {"customerIds":[5,19],"email":"bob@trades.example"}]
```

Build: 0 Warning(s), 0 Error(s). `dotnet run` starts the API;
curl confirms all endpoints respond correctly.

## Discipline signal

This is the third EXT commit of the session (CRM demo sample #141,
CRM scenario tests in #143, now this API). The live-lock audit's
inaugural lesson explicitly prescribed shipping external-priority
increments when the smell fires. Three landed this session, all on
priority #1 (ServiceTitan + UI) — the factory is correctly
response-pattern even before any of tonight's PRs merge to main.

## What this does NOT do

- Does NOT wire Postgres — in-memory only for v0; Npgsql wiring is
  a follow-up PR once Aaron confirms the DB driver
- Does NOT expose Zeta / DBSP / retraction-native language to the
  frontend — standard CRUD shape per the ServiceTitan positioning
  directive
- Does NOT implement writes — v0 is read-only; POST/PUT/DELETE is
  a follow-up
- Does NOT add auth — no authentication for v0
- Does NOT ship docker-compose — future PR bundles this API with
  Postgres in one command

Composes with:
- `samples/ServiceTitanFactoryDemo/` (SQL schema + seed) — sibling,
  same shapes; v1 wires this API to that schema
- `docs/plans/servicetitan-crm-ui-scope.md` — build sequence step 1
  (API skeleton) complete; step 2 (DB wiring) is next
- `memory/feedback_servicetitan_demo_sells_software_factory_not_zeta_database_2026_04_23.md`
- `memory/feedback_lesson_permanence_is_how_we_beat_arc3_and_dora_2026_04_23.md`

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples: ServiceTitan factory-demo C# companion API — parity with F# sibling

ServiceTitan uses C# for most of their backend with zero F#. Shipping
a C# companion to the F# API (#146) so ST engineers evaluating the
factory see code in the language they already read fluently.
F# stays the reference — it's closer to math, theorems are easier to
express — but factory output matches audience stack.

## What lands

- `ServiceTitanFactoryApi.CSharp.csproj` — `Microsoft.NET.Sdk.Web`,
  nullable + implicit usings enabled, TreatWarningsAsErrors
- `Customer.cs`, `Opportunity.cs`, `Activity.cs` — records, one
  per file (MA0048)
- `Seed.cs` — deterministic in-memory seed, identical to F# Seed.fs:
  20 customers, 30 opportunities, 33 activities, 2 intentional
  email collisions
- `Program.cs` — 9 minimal-API endpoints, identical routes + JSON
  shapes to the F# sibling
- `README.md` — parity guarantee, design notes, C# specifics

## Smoke-test parity (verified)

```
GET /api/pipeline/funnel
[{"stage":"Lead","count":10,"totalCents":5400000}, ...5 stages]

GET /api/pipeline/duplicates
[{"email":"alice@acme.example","customerIds":[1,13]},
 {"email":"bob@trades.example","customerIds":[5,19]}]

GET /api/customers  -> 20 customers
```

Same seed, same shapes, same numbers as the F# version (#146).
Frontends switch between them without code changes.

## Analyzer discipline passes

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer.CSharp +
Meziantou.Analyzer + Microsoft .NET Analyzers pack active. The C#
companion respects every rule the F# version's discipline
already encodes implicitly — StringComparer.Ordinal for GroupBy,
static-readonly for endpoint list, record-per-file, no-var-discarded.

## Discipline signal

Fourth EXT commit of the session (CRM demo #141, CRM scenario tests
#143, F# API #146, now this C# API). All on Aaron's priority #1.
The live-lock audit's inaugural lesson prescribed "ship external-
priority increments when smell fires" — four landed in one session.

## Factory-pitch moment

This pair (F# + C# from the same spec, identical behaviour) is a
concrete factory-capability signal. The software factory produces
code in your stack, to your analyzer discipline, with parity across
languages. The pitch isn't "pick our language"; it's "your language,
enforced by our quality floor."

## What this does NOT do

- Does NOT rewrite or deprecate the F# sibling — both live
- Does NOT wire Postgres — same v0 scope
- Does NOT leak Zeta / DBSP / retraction-native concepts to the
  ST-facing surface
- Does NOT claim the C# version is the primary — F# is reference

Composes with:
- `samples/ServiceTitanFactoryApi/` (F# sibling)
- `memory/project_zeta_f_sharp_reference_c_sharp_and_rust_future_servicetitan_uses_csharp_2026_04_23.md`
- `memory/feedback_servicetitan_demo_sells_software_factory_not_zeta_database_2026_04_23.md`

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* rename: generic FactoryDemo.Api.CSharp (was ServiceTitanFactoryApi.CSharp)

Aaron 2026-04-23 directive:

> lets try to reduce the number of class and thing we call servce titan
> or this will be confusing in a Zeta repo. ... this is not a service
> titan repo, it's an open source repo.

Plus, 2026-04-23 follow-up on language priority:

> c# is a more popular language than f# so it makes sense to start
> with a factory c# demo anyways

## What renames

- `samples/ServiceTitanFactoryApi.CSharp/` →
  `samples/FactoryDemo.Api.CSharp/`
- Project name + csproj filename same rename
- `RootNamespace` `Zeta.Samples.ServiceTitanFactoryApi` →
  `Zeta.Samples.FactoryDemo.Api`
- `namespace` declarations in .cs files match
- Zeta.sln project entry updated
- README rewritten to generic framing (C# is the popular
  .NET language; demo starts there; F# stays reference)
- Root endpoint name field `"ServiceTitan factory-demo API (C#)"` →
  `"Factory-demo API (C#)"`
- All doc cross-references updated to new path names

Build: 0 Warning(s), 0 Error(s) with the full SonarAnalyzer +
Meziantou + Microsoft .NET Analyzers pack. Behaviour unchanged —
same 9 endpoints, same JSON shapes, same seed.

Memory rule:
`memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md`
captures the positioning directive in durable form so future
agents don't re-introduce company-specific names.

Sibling renames land in separate PRs / branches:
- F# API sibling (currently PR #146 / ServiceTitanFactoryApi)
- DB scaffold (PR #145 / ServiceTitanFactoryDemo)
- CRM kernel sample (PR #141 / ServiceTitanCrm)
- CRM-UI scope doc (PR #144 / docs/plans/servicetitan-crm-ui-scope.md)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* FactoryDemo.Api.CSharp: smoke-test.sh — end-to-end endpoint + contract verification

I chose to land this because the JSON-shape parity claim we make
in the README ("byte-identical shapes between F# and C# versions")
needs a machine-verifiable check. A smoke test on the C# side is the
first half; the F# sibling gets the same pattern in a follow-up.

Starts the API on a random port, waits up to 10s for readiness,
then runs 19 checks against all 9 endpoints:

  - Root metadata: name, version, endpoints length
  - Collection lengths: customers (20), opportunities (30), activities (33)
  - Single-item lookup: customer #1 name, opportunity #1 stage
  - Per-customer activities: customer #1 has 4
  - Pipeline funnel counts per stage: Lead 10, Qualified 6, Won 6, Lost 2
  - Pipeline funnel totals in cents: Lead $54k, Won $26.7k
  - Duplicates: 2 pairs, (1,13) share alice@acme, (5,19) share bob@trades
  - 404 behaviour: missing customer returns 404

Shuts the API down cleanly on exit via trap + kill.

```
$ bash samples/FactoryDemo.Api.CSharp/smoke-test.sh
Building API...
Starting API on http://localhost:5235...

Factory-demo C# API smoke test
==============================
  OK   root.name contains 'Factory-demo'                  (true)
  OK   root.version                                       (0.0.1)
  OK   root.endpoints length                              (5)
  OK   /api/customers length                              (20)
  ...
  OK   missing customer HTTP status                       (404)

All checks passed.
```

dotnet, curl, jq — all standard dev tools. The demo does not ask
for anything exotic. Matches the FactoryDemo.Db smoke-test.sh
pattern on the sibling branch.

- Random high port (5100-5499) instead of fixed — reduces collision
  with other dev services.
- `curl -sf` for normal checks, `curl -o /dev/null -w "%{http_code}"`
  for the 404 case — the two paths have different error semantics so
  I use different tools for each.
- Shape-level assertions against numeric counts rather than raw JSON
  diff — makes the test tolerant of property-ordering differences
  between serializers. The parity claim is about *shape*, not byte-
  identity, so this matches intent.
- Trap + kill on EXIT — guarantees the API stops even on test
  failure or ctrl-C. No leaked background processes.

- Does NOT test the F# sibling. Same-pattern smoke-test for
  FactoryDemo.Api.FSharp lands in its branch (or a follow-up
  PR on that branch).
- Does NOT diff F# vs C# outputs directly. A cross-language
  parity-diff test composes better as a separate tool once both
  APIs have merged.
- Does NOT wire to Postgres. In-memory seed only; docker-compose
  + DB wiring is a separate PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* samples+audit: PR #147 review-drain — sln BOM, signal-quality empty-case, audit fail-hard, endpoint lists

Drains 14 unresolved review threads on PR #147 (FactoryDemo.Api.CSharp):
- Zeta.sln: strip leading blank line so 'Microsoft Visual Studio
  Solution File' is the first line (threads #2 #3).
- SignalQuality.fs: compressionRatio on empty input was 1.0, which
  composed as Quarantine via severityOfScore — flipped to 0.0 and
  added explicit empty-input Pass finding in compressionMeasure;
  also dropped unused System.Runtime.CompilerServices open
  (threads #4 #5).
- live-lock-audit.sh: fail hard (exit 2) when origin/main is not
  resolvable so a missing-remote CI checkout can't silently report
  'No commits found' -> healthy; switched --stat|awk file-list
  extraction to git diff-tree --name-only plumbing form
  (threads #1 #6).
- ServiceTitanFactoryApi README + Seed.fs: remove dead memory/
  and docs/plans/ links; replace Aaron's-name reference with
  'human maintainer' role wording; drop non-existent sibling
  SQL-seed refs (threads #7 #8 #9).
- FactoryDemo.Api.CSharp README + Program.cs + Seed.cs: fix dead
  refs to samples/FactoryDemo.Api.FSharp/ and samples/FactoryDemo.Db/
  to point at the real F# sibling samples/ServiceTitanFactoryApi/
  and to a BACKLOG row for the Postgres-backed follow-up
  (threads #11 #14).
- Program.cs + Program.fs: root endpoint index now advertises all
  9 routes including the parameterised {id} routes, matching the
  README tables (threads #12 #13).
- Thread #10 (project naming 'ServiceTitanFactoryApi.CSharp' in PR
  description): resolved in-thread — code/namespace already
  consistent (Zeta.Samples.FactoryDemo.Api); fix is PR-description-
  only, not code.

Build: dotnet build -c Release -> 0 Warning(s) 0 Error(s).

* drain PR #147: post-rebase thread fixes — test-empty-ratio + smoke-endpoint-count

- tests/Tests.FSharp/Algebra/SignalQuality.Tests.fs: test asserted 1.0 for
  compressionRatio on empty input, but the fix in 16ad746 changed the
  convention to 0.0 (neutral = clean, not maximally suspicious). Updated
  the test expectation + name + comment to match the current code.
- samples/FactoryDemo.Api.CSharp/smoke-test.sh: root.endpoints length
  expectation was 5; Program.cs now advertises 8 routes in the index
  (post 16ad746 expansion). Corrected the smoke-test assertion.

Rebased onto origin/main (which advanced via #146 FactoryDemo.Api.FSharp
merge); Zeta.sln conflicts resolved by keeping both FactoryDemo.Api.FSharp
and the ServiceTitanCrm/samples solution-folder additions.

Build gate: 0 Warning(s) / 0 Error(s) in Release.

* PR #147 review-drain — Copilot pass on b4f5a49

Addresses five unresolved review threads:

- drop/README.md: sweep name attribution to "the human
  maintainer" role-ref (BP-name-attribution).
- samples/FactoryDemo.Api.CSharp/Program.cs: fix endpoint
  comment "9 concrete endpoints" → "8 API endpoints besides
  `/`" (array has 8; root excluded).
- samples/FactoryDemo.Api.CSharp/smoke-test.sh: per-run log
  via mktemp (collision-safe + non-/tmp-host-safe); print
  path on failure + success.
- samples/ServiceTitanFactoryApi/: delete stale F# sibling
  dir (PR #146 already landed FactoryDemo.Api.FSharp on
  main with identical code); drop duplicate sln Project
  block + config duplicates; fix CSharp refs to point at
  the surviving FactoryDemo.Api.FSharp/.

Fifth thread (SignalQuality scope-creep) is judgment —
branch history is deep; splitting now adds more churn than
value. Replying with backlog-and-resolve per three-outcome.

* PR #147 review-drain — 7 threads (Copilot + Codex)

Threads drained:
- btw.md: name attribution -> "human maintainer" / "the maintainer" (Copilot P1, AGENT-BEST-PRACTICES.md:284-292)
- live-lock-audit.sh: add --root to git diff-tree so root commit classifies correctly (Copilot P2)
- FactoryDemo.Api.CSharp Program.cs: add "/" to endpoints list for F# parity; bump smoke-test length 8->9 (Copilot P1 + Codex P2, same fix)
- FactoryDemo.Api.CSharp smoke-test.sh: reword mktemp comment to describe system temp dir accurately (Copilot P2)
- ServiceTitanCrm -> FactoryDemo.Crm: rename dir, fsproj, module namespace, RootNamespace, sln entry, test doc-comment; drop stale ServiceTitanFactoryApi bin+obj (Copilot P1, memory/feedback_open_source_repo_demos_stay_generic_not_company_specific_2026_04_23.md:59-66)
- SignalQuality.fs: compressionRatio + compressionMeasure short-circuit to 0.0 (Pass) below 64-byte threshold to avoid gzip-header-dominates Quarantine of legitimate short strings (Codex P1)

Drain log: docs/pr-preservation/147-drain-log.md preserves each thread verbatim (git-native high-signal preservation).

dotnet build -c Release: 0 Warning(s), 0 Error(s).

* PR #147 review-drain second pass — 4 fix-inline + 3 scope-bleed

- Seed.cs + Seed.fs: rename contact 13 'Aaron Smith' -> 'Acme Contact
  (new lead)' (Copilot P2 name-attribution, parity preserved across
  C# / F# siblings).
- drop/README.md: correct 'only tracked file' wording to reflect the
  README.md + .gitignore two-sentinel design (Copilot P2).
- tools/audit/live-lock-audit.sh: docstring attribution 'Aaron's ...'
  -> 'Human-maintainer ...' (Copilot P1); add '-m' plus 'sort -u' to
  'git diff-tree' so merge commits bucket on their real files instead
  of mis-classifying as OTHR (Codex P1 — was skewing EXT/INTL/SPEC %
  and could disable the live-lock gate after a round of merges).
- docs/pr-preservation/147-drain-log.md: append second-pass per-thread
  audit trail (git-native preservation).

Three threads resolved as scope-bleed / already-addressed: operator-
input-quality-log.md (file not in PR diff, landed via 204bbb6 on
main), AUTONOMOUS-LOOP.md (file not in PR diff, zero Aaron on HEAD),
Tests.FSharp.fsproj (both SignalQuality + CrmScenarios already listed
at lines 26 and 49).

Build: 0W/0E. Audit sanity: live-lock-audit.sh still healthy with
merges now bucketed correctly.

* fix: markdownlint MD001/MD022/MD032 on #147 drain-log (h3→h2 on Thread headers)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* drain: resolve 11 threads on #147 (mix FIX + BACKLOG + Otto-256 reject)

Thread-by-thread outcomes across the 11 unresolved review threads on PR
#147 (5 FIX, 2 BACKLOG, 2 Otto-256 REJECT, 2 already-addressed/stale):

FIXES (code):
- live-lock-audit.sh: replace `git show --stat` with explicit
  `git log -1 -m --first-parent --name-only` so merge commits classify
  against parent-1 only (the landing side). The prior `git show` form
  risked combined-diff semantics in some git versions; the explicit
  form is first-parent by construction (Codex P1).
- SignalQuality.fs: restore `compressionMinInputBytes = 64` threshold
  (dropped by the f1dc2bb merge-conflict resolution) and mark it
  `private` so it is not part of the public API surface (Copilot).
  Short-circuits `compressionRatio` + `compressionMeasure` to 0.0 for
  sub-threshold inputs, avoiding spurious Quarantine on short legitimate
  strings. Evidence reports UTF-8 byte count (consistent with the
  threshold's units) instead of `text.Length` chars (Copilot). Adjusted
  the empty-string test to assert the new 0.0 neutral value.
- smoke-test.sh: replace non-portable `mktemp -t <template>` with a
  pre-constructed absolute-path template rooted at `${TMPDIR:-/tmp}`
  where XXXXXX is the tail (BSD/macOS requires tail-XXXXXX; GNU accepts
  either). `.log` extension is appended via `mv` after creation so the
  single invocation is cross-platform (Copilot x2 — threads 4 + 10).
- CrmScenarios.Tests.fs: update doc-comment `samples/FactoryDemo.Crm`
  -> `samples/CrmSample` to match the canonical sample path on main
  (Copilot).

BACKLOG (deferred P2):
- Smoke-test deterministic port allocation (Codex P2) — replace
  RANDOM-in-range with OS-assigned ephemeral port via `--urls
  http://127.0.0.1:0` and log-line parse.
- FactoryDemo.Api.CSharp solution project-type GUID hygiene (Copilot)
  — align with modern SDK-style GUID used by other C# projects.

OTTO-256 REJECT (history-file exemption):
- docs/pr-preservation/147-drain-log.md (Copilot) and
  docs/hygiene-history/live-lock-audit-history.md (Copilot): both
  requested stripping first-name "Aaron" attributions. Declined per
  Otto-256 (2026-04-24) — history files exempt from the "no name
  attribution" rule; a P2 BACKLOG row already exists
  (`## P2 — FACTORY-HYGIENE — name-attribution policy clarification
  (history-file exemption)`) to codify this in AGENT-BEST-PRACTICES.md.

ALREADY-ADDRESSED (stale reviewer context):
- drop/README.md heading (Copilot): Copilot flagged "one tracked
  sentinel" but the current heading reads "two tracked sentinels"
  (fixed in a prior drain). Resolving as addressed.

Build: `dotnet build -c Release` -> 0 Warning(s), 0 Error(s).
Tests: `dotnet test --filter "FullyQualifiedName~SignalQuality"` ->
  22/22 pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…tion (Amara #3 correction)

Applies Amara 17th-ferry Part 2 correction #3: replace muddy
'subgraph entropy collapse' with explicit cohesion / exclusivity
/ conductance metrics used in the cartel-detection literature
(Wachs & Kertész 2019).

Surface (3 new primitives):
- Graph.internalDensity : Set<'N> -> Graph<'N> -> double option
  Internal edge weight / ordered-pair count. High value = tight
  sub-cluster.
- Graph.exclusivity : Set<'N> -> Graph<'N> -> double option
  Internal weight / total-outgoing weight. Near 1 = cartel
  isolated; near its relative share = integrated community.
- Graph.conductance : Set<'N> -> Graph<'N> -> double option
  Classical cut-to-volume ratio. Low = tight isolation.

All three return None on degenerate inputs (size < 2 for
density; empty set for exclusivity; empty/full for conductance).

Tests (6 new, 37 total in GraphTests, all passing):
- internalDensity None on |S| < 2
- internalDensity of K3 clique ≈ 10 (weight 10 per pair;
  ordered-pair count 6; density = 60/6)
- exclusivity = 1 for isolated K3
- exclusivity < 1 but > 0.9 for K3 + 1 external edge
- conductance < 0.1 for well-isolated K3 subset (bridged by
  thin edge to another K3)
- conductance None on empty or full-graph subset

Why this set:
Amara's verification found 'subgraph entropy collapse' as
stated was mathematically muddy — uniform dense clique has
HIGH entropy over internal edges if weights are equal.
Cohesion (internalDensity) + exclusivity + conductance
capture cluster-like structure directly + are standard in
the economic/sociological cartel-detection literature.
Entropy can remain as secondary descriptor but these three
are the primary group-level features.

15th graduation under Otto-105 cadence. Applies 1 of 5 future-
graduation items from Amara 17th-ferry verification pass.

Next graduation queue (remaining from Amara Otto-132
corrections):
- Windowed stake covariance acceleration (#4)
- Event-stream → phase pipeline for PLV (#5)
- Robust-z-score variant of coordinationRiskScore (#4 robust
  statistics)

Build: 0 Warning / 0 Error.

Provenance:
- Concept: Aaron (trivial cartel detect — first-order-signal
  tier)
- Formalization: Wachs & Kertész 2019 (co-bidding network
  cohesion/exclusivity) via Amara's 14th + 17th ferries
- Implementation: Otto (15th graduation)

Composes with:
- Graph.labelPropagation (PR #326) for community → subset input
- RobustStats.robustAggregate (PR #295) for aggregating
  density/exclusivity/conductance across many candidate
  subsets outlier-resistantly

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…leration — 15th+16th graduation consolidated

Consolidates the DIRTY #329 cohesion primitives (Amara 17th-ferry
correction #3) with the new StakeCovariance module (Amara
correction #4).

Content from closed PR #329 (resurrect):
- Graph.internalDensity / exclusivity / conductance
- Wachs & Kertész 2019 cartel-detection cohesion/exclusivity
  replacing muddy 'subgraph entropy collapse'

NEW content (Amara correction #4):
- Zeta.Core.StakeCovariance module with:
  - windowedDeltaCovariance : int -> double[] -> double[] -> double option
    Pairwise cov over sliding window of stake-delta series
  - covarianceAcceleration : double option -> double option ->
    double option -> double option
    2nd-difference of three consecutive cov values
    (A(t) = C(t) - 2·C(t-1) + C(t-2))
  - aggregateAcceleration : Map<int * int, double> -> double option
    Mean pairwise acceleration over candidate group

Why a separate module: StakeCovariance operates on raw stake-
delta time series, not Graph edges. Composes WITH Graph via
downstream detector that combines graph signals + covariance
signals + sync signals into the full CoordinationRiskScore.

Addresses Amara's Part 2 correction #4 ambiguity: her Part 1
had 'C(t) = Cov({s_i(t)}, {s_j(t)})' which is undefined at a
single timepoint. This ship implements the windowed-delta +
2nd-difference formulation from her correction.

Tests (10 new, 44 total in GraphTests, all passing):
- internalDensity None on |S|<2
- internalDensity of K3 weight-10 ≈ 10
- exclusivity = 1 for isolated K3
- conductance < 0.1 for well-isolated subset
- windowedDeltaCovariance: None on too-small series
- windowedDeltaCovariance: high positive for synchronized motion
- windowedDeltaCovariance: negative for anti-correlated motion
- covarianceAcceleration = 2nd difference of cov series
- covarianceAcceleration None when any input missing
- aggregateAcceleration averages across pairs

4 of 8 Amara 17th-ferry corrections now shipped (#1 K₃=2 ✓,
conductance ✓, #4 windowed stake covariance acceleration ✓).
Remaining: #5 event→phase pipeline (future); #4 robust-z-score
variant of composite (future); #6 + #7 + #8 doc-phrasing /
BACKLOG.

Build: 0 Warning / 0 Error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…6th consolidated (Amara corrections #3+#4) (#331)

* core: Graph cohesion (#329 resurrect) + StakeCovariance windowed acceleration — 15th+16th graduation consolidated

Consolidates the DIRTY #329 cohesion primitives (Amara 17th-ferry
correction #3) with the new StakeCovariance module (Amara
correction #4).

Content from closed PR #329 (resurrect):
- Graph.internalDensity / exclusivity / conductance
- Wachs & Kertész 2019 cartel-detection cohesion/exclusivity
  replacing muddy 'subgraph entropy collapse'

NEW content (Amara correction #4):
- Zeta.Core.StakeCovariance module with:
  - windowedDeltaCovariance : int -> double[] -> double[] -> double option
    Pairwise cov over sliding window of stake-delta series
  - covarianceAcceleration : double option -> double option ->
    double option -> double option
    2nd-difference of three consecutive cov values
    (A(t) = C(t) - 2·C(t-1) + C(t-2))
  - aggregateAcceleration : Map<int * int, double> -> double option
    Mean pairwise acceleration over candidate group

Why a separate module: StakeCovariance operates on raw stake-
delta time series, not Graph edges. Composes WITH Graph via
downstream detector that combines graph signals + covariance
signals + sync signals into the full CoordinationRiskScore.

Addresses Amara's Part 2 correction #4 ambiguity: her Part 1
had 'C(t) = Cov({s_i(t)}, {s_j(t)})' which is undefined at a
single timepoint. This ship implements the windowed-delta +
2nd-difference formulation from her correction.

Tests (10 new, 44 total in GraphTests, all passing):
- internalDensity None on |S|<2
- internalDensity of K3 weight-10 ≈ 10
- exclusivity = 1 for isolated K3
- conductance < 0.1 for well-isolated subset
- windowedDeltaCovariance: None on too-small series
- windowedDeltaCovariance: high positive for synchronized motion
- windowedDeltaCovariance: negative for anti-correlated motion
- covarianceAcceleration = 2nd difference of cov series
- covarianceAcceleration None when any input missing
- aggregateAcceleration averages across pairs

4 of 8 Amara 17th-ferry corrections now shipped (#1 K₃=2 ✓,
conductance ✓, #4 windowed stake covariance acceleration ✓).
Remaining: #5 event→phase pipeline (future); #4 robust-z-score
variant of composite (future); #6 + #7 + #8 doc-phrasing /
BACKLOG.

Build: 0 Warning / 0 Error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* core: address PR #331 review on Graph + StakeCovariance

- Fix conductance full-subset check: intersect S with the
  graph's node set instead of comparing |S| = |V|. Subsets
  containing nodes outside the graph could match by count
  alone and erroneously return None.
- Fix internalDensity self-loop accounting: exclude s = t
  from the numerator so the sum aligns with the
  |S|·(|S|-1) ordered-distinct-pair denominator.
- windowedDeltaCovariance now requires equal-length input
  series (returns None on mismatch) so the trailing window
  aligns by time index rather than silently truncating the
  longer series. Doc reflects that constant / zero-variance
  windows return Some 0.0 (covariance is well-defined and
  zero, not undefined). Population covariance is intentional
  and now documented.
- aggregateAcceleration is generic over the node-key type
  ('N when 'N : comparison) for API consistency with
  Graph<'N>; switched the average to a single-pass Map.fold
  to drop the intermediate array allocation.
- Drop [<AutoOpen>] on the StakeCovariance module so
  Graph.fs doesn't auto-open two namespaces' worth of
  identifiers into Zeta.Core. Tests already opened the
  module explicitly; relocated that open to the top of the
  test file alongside other opens.
- Strip ferry / correction-number lineage from doc
  comments per the code-comments-explain-code rule.

* docs: PR #331 drain log + StakeCovariance file-split backlog row

Adds the per-thread drain log under
docs/pr-preservation/331-drain-log.md (verbatim reviewer
comments + outcomes + replies + resolution commit) and a
P2 backlog row capturing the StakeCovariance file-split
follow-up flagged in thread 2.

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…Corrections

Two-part ferry from Aaron Otto-157/158 tick boundary:

Part 1 — Deep research on Cartel-Lab calibration + CI hardening
  (~4000 words; 8 sections A-H + action items + Mermaid diagrams):
  - Null-models table (6 types: Erdős-Rényi, configuration,
    stake-shuffle, temporal-shuffle, clustered-honest, noise)
  - CoordinationRiskScore formula with 6 robust-z terms +
    default weights α=β=0.20, γ=ε=0.15, δ=0.20, η=0.10
  - 8-row adversarial scenario table (obvious clique → stealth
    → synchronized voting → honest cluster → low-weight →
    camouflage → rotating → cross-coalition)
  - 4-PR roadmap: seed-lock/CI governance → calibration harness
    → adversarial scenarios → docs/promotion criteria
  - KSK/Aurora integration: advisory-only flow
    (Detection → Oracle → KSK → Action)
  - "What not to claim" caveats (6 items: no proof of intent,
    not all collusion detectable, not production-ready, etc.)

Part 2 — Amara's own GPT-5.5 Thinking correction pass on Part 1
  (~1500 words; 10 required corrections; repo-safe status
  statement; corrected promotion ladder + PR roadmap titles):
  - #1: replace "CI confirms" with "PR #323 clears toy
    falsifiability bar"
  - #2: Wilson intervals replace handwave ±5% CI (90/100 →
    LB only 82.6%; 20/100 FPR → UB 28.9%)
  - #3: rename "Cartel Score" → "CoordinationRiskScore" locked
  - #4: conductance sign flip — use Z(-conductance) or
    Z(exclusivity), not Z(+conductance)
  - #5: modularity relational — use Q(attacked)-Q(baseline)>θ
    not absolute Q thresholds
  - #6: PLV phase-offset — PLV=1 can mean anti-phase; need
    magnitude AND mean phase offset
  - #7: MAD=0 fallback — epsilon floor or percentile-rank
  - #8: replace Medium-article source with scikit-learn
    precision-recall docs
  - #9: explicit artifact output layout
    (calibration-summary.json, seed-results.csv, etc.)
  - #10: sharder — measure variance before widening threshold

Corrected promotion ladder (0-6 stages):
  0 Theory / 1 Toy detector / 2 Calibration harness /
  3 Scenario suite / 4 Advisory engine / 5 Governance integration /
  6 Enforcement candidate

PR #323 is Stage 1, NOT Stage 4.

Otto's operationalization notes:
- 4/10 corrections already aligned with shipped substrate:
  #4 exclusivity (PR #331), #5 modularity relational
  (PR #324), #7 MAD floor (PR #333), #10 sharder Otto-132
  (BACKLOG #327).
- 6/10 queued as future graduations: Wilson CIs in tests;
  MAD=0 percentile-rank fallback; conductance-sign doc;
  PLV phase-offset extension; CI test classification;
  artifact-output layout.

Invariant restated (Amara 16th-ferry carry-over):
  "Every abstraction must map to a repo surface, a test,
   a metric, or a governance rule."

Cross-ref verified: PRs #321 #323 #324 #326 #327 #331 #332
#333, docs/definitions/KSK.md (Otto-157 / #336), 17th ferry
(#330), 16th ferry, 15th ferry, Otto-140..145 memory.

GOVERNANCE §33 four-field header (Scope / Attribution /
Operational status / Non-fusion disclaimer).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ns (10 tracked; 4 already shipped, 6 queued) (#337)

* ferry: Amara 18th absorb — Calibration + CI Hardening + 5.5-Thinking Corrections

Two-part ferry from Aaron Otto-157/158 tick boundary:

Part 1 — Deep research on Cartel-Lab calibration + CI hardening
  (~4000 words; 8 sections A-H + action items + Mermaid diagrams):
  - Null-models table (6 types: Erdős-Rényi, configuration,
    stake-shuffle, temporal-shuffle, clustered-honest, noise)
  - CoordinationRiskScore formula with 6 robust-z terms +
    default weights α=β=0.20, γ=ε=0.15, δ=0.20, η=0.10
  - 8-row adversarial scenario table (obvious clique → stealth
    → synchronized voting → honest cluster → low-weight →
    camouflage → rotating → cross-coalition)
  - 4-PR roadmap: seed-lock/CI governance → calibration harness
    → adversarial scenarios → docs/promotion criteria
  - KSK/Aurora integration: advisory-only flow
    (Detection → Oracle → KSK → Action)
  - "What not to claim" caveats (6 items: no proof of intent,
    not all collusion detectable, not production-ready, etc.)

Part 2 — Amara's own GPT-5.5 Thinking correction pass on Part 1
  (~1500 words; 10 required corrections; repo-safe status
  statement; corrected promotion ladder + PR roadmap titles):
  - #1: replace "CI confirms" with "PR #323 clears toy
    falsifiability bar"
  - #2: Wilson intervals replace handwave ±5% CI (90/100 →
    LB only 82.6%; 20/100 FPR → UB 28.9%)
  - #3: rename "Cartel Score" → "CoordinationRiskScore" locked
  - #4: conductance sign flip — use Z(-conductance) or
    Z(exclusivity), not Z(+conductance)
  - #5: modularity relational — use Q(attacked)-Q(baseline)>θ
    not absolute Q thresholds
  - #6: PLV phase-offset — PLV=1 can mean anti-phase; need
    magnitude AND mean phase offset
  - #7: MAD=0 fallback — epsilon floor or percentile-rank
  - #8: replace Medium-article source with scikit-learn
    precision-recall docs
  - #9: explicit artifact output layout
    (calibration-summary.json, seed-results.csv, etc.)
  - #10: sharder — measure variance before widening threshold

Corrected promotion ladder (0-6 stages):
  0 Theory / 1 Toy detector / 2 Calibration harness /
  3 Scenario suite / 4 Advisory engine / 5 Governance integration /
  6 Enforcement candidate

PR #323 is Stage 1, NOT Stage 4.

Otto's operationalization notes:
- 4/10 corrections already aligned with shipped substrate:
  #4 exclusivity (PR #331), #5 modularity relational
  (PR #324), #7 MAD floor (PR #333), #10 sharder Otto-132
  (BACKLOG #327).
- 6/10 queued as future graduations: Wilson CIs in tests;
  MAD=0 percentile-rank fallback; conductance-sign doc;
  PLV phase-offset extension; CI test classification;
  artifact-output layout.

Invariant restated (Amara 16th-ferry carry-over):
  "Every abstraction must map to a repo surface, a test,
   a metric, or a governance rule."

Cross-ref verified: PRs #321 #323 #324 #326 #327 #331 #332
#333, docs/definitions/KSK.md (Otto-157 / #336), 17th ferry
(#330), 16th ferry, 15th ferry, Otto-140..145 memory.

GOVERNANCE §33 four-field header (Scope / Attribution /
Operational status / Non-fusion disclaimer).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* ferry: fix markdownlint MD018 — line-start #221 parsed as H1 heading

* ferry: drain PR #337 review threads — 4 FIX, 2 NARROW+BACKLOG, 8 BACKLOG+RESOLVE

Factory-authored sections of the 18th-ferry absorb (header,
Otto's notes, Cross-references) edited under name-attribution
+ code-comments-not-history disciplines; Amara's verbatim
Part 1 + Part 2 body left intact per verbatim-preserve.

In-doc edits:
- Soften "verified against actual" wording on the
  CLAUDE.md cross-reference bullet to anchor-list
  rechecked-at-drain-time framing.
- Use full `tests/Tests.FSharp/Simulation/` path in the
  Stage-discipline section (was bare `tests/Simulation/`).
- Replace dead "GOVERNANCE §33" cite with
  factory-convention + CLAUDE.md ground-rule pointer
  (numbered §33 not yet landed; rule is captured
  by convention across docs/aurora/** absorbs).
- Drop broken `feedback_ksk_naming_*.md` filename and
  soften 15th/16th ferry cross-refs to "not present as a
  dedicated absorb in this snapshot."

Drain-log: docs/pr-preservation/337-drain-log.md per
Otto-250.

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ng design (8th-ferry candidate #3) (#282)

* research: provenance-aware bullshit-detector — engineering-facing design (8th-ferry candidate #3)

M-effort engineering-facing design doc. Formalises the scoring
layer sketched in the semantic-canonicalization spine (PR #280
Otto-98), integrating Aminata's 3 CRITICAL concerns from
oracle-scoring v0 pass (PR #263) at write-time.

Composition stack (built top-down on spine):

- Input canonicalisation / representation / ANN retrieval =
  delegated to spine (Otto-98 PR #280 layers 1-3).
- Provenance-cone computation via citations-as-first-class
  lineage graph traversal.
- **5-gate band classifier** replaces Amara's decimal
  formulation (α·sim + β·evidence - γ·carrierOverlap -
  δ·contradiction → bands). Same pattern as oracle-scoring
  v0.

5 gates per candidate: G_similarity / G_evidence_independent
/ G_carrier_overlap / G_contradiction / G_status. Band merge
= min over gates; RED<YELLOW<GREEN. Query-level aggregation =
worst-band across retrieved candidates.

5 output types (Amara's set, mapped to bands):
- supported (GREEN)
- looks similar but lineage-coupled (YELLOW via
  G_carrier_overlap)
- plausible but unresolved (YELLOW via G_status / G_evidence)
- likely confabulated (RED via G_evidence + high similarity)
- known-bad pattern (RED via G_status)

Plus default `no-signal` when retrieval returns empty.

Aminata's 3 CRITICAL concerns addressed at write-time:
- Gameable-by-self-attestation → G_evidence_independent
  requires independent-oracle verification for GREEN;
  self-attested only reaches YELLOW.
- Parameter-fitting → parameter-change-ADR-gate pattern;
  parameter_file_sha bound into every receipt.
- False-precision → band output not decimal; ordinal-in-
  ordinal-out.

PatternLedger status-pinning requires pinned_by +
pinned_reason + optional second-reviewer per decision-proxy-
evidence schema (PR #222) to prevent same-agent-self-
reinforcement drift.

Worked example: this doc itself as query q. Detector
correctly classifies it as `looks similar but lineage-
coupled` — the detector flags its own carrier-laundered
convergence with sources. Self-demonstrates the discipline.

Module implementation sketch follows KSK-as-Zeta-module
template (PR #259): 10 typed interfaces + 4 canonical views
+ 3 event types including DetectorOutputRetracted for ADR-
driven threshold-change retractions.

Scope limits (7 items): no implementation; no parameter
values; no human-review replacement; no claim of
completeness; no auto-promotion of PatternLedger status
pins; no extension beyond Zeta substrate; no precision/
recall quantification.

8 dependencies-to-adoption in priority order: Aminata 4th
pass (anticipated concerns already integrated but adversarial
review surfaces more); candidate #4 operational promotion;
independent-oracle substrate; parameter-change-ADR template;
PatternLedger event stream; property tests; embedding+ANN
library choices; F#/.NET implementation.

Archive-header format self-applied — 16th aurora/research doc
in a row.

Lands within-standing-authority per Otto-82/90/93 calibration.

Closes 8th-ferry candidate #3. **4/5 substantive responses
closed** across Otto-96/97/98/99 — matches 5th-ferry 4/4-
artifact closure arc. Remaining #4 `docs/EVIDENCE-AND-
AGREEMENT.md` future operational promotion gated on #3 +
Aminata pass.

Otto-99 tick primary deliverable.

* rename: bullshit-detector → claim-veracity-detector (drop wisecrack-as-canonical-name)

Maintainer 2026-04-24: "i don't like the name bullshit-detector
... that was as wise crack i said to amara that she kept saying."

The wisecrack got promoted to canonical title across the
research doc + PR title + filename. Otto-237 mention-vs-adoption
discipline applies — wisecracks can be MENTIONED in conversation
history but should NOT be ADOPTED as factory vocabulary.

Replacements (7 across the research doc):
  bullshit detector       → claim-veracity detector
  bullshit-detector       → claim-veracity-detector
  bullshitRisk            → claimVeracityRisk
  all bullshit            → an unsupported claim
  every form of bullshit  → every form of unsupported claim
  Bullshit-detector       → Claim-veracity-detector

Filename also renamed:
  docs/research/provenance-aware-bullshit-detector-2026-04-23.md
  → docs/research/provenance-aware-claim-veracity-detector-2026-04-23.md

PR title rename owed via gh pr edit. Branch name stays as-is —
ephemeral, cleans up post-merge.

* drain: address Copilot review on #282 — gate-name consistency, evidence-gate conditionality, schema fields, DRIFT-TAXONOMY ref, MD032

- Fix gate-name inconsistency: G_evidence → G_evidence_independent
  in band-merging formula and 5-output-type mapping (matches
  the gate name in the table on line 134).
- Reconcile internal contradiction in Concern 1 (evidence-gates-
  GREEN): make conditional explicit. Until independent-oracle
  substrate exists, gate is ADVISORY ONLY and does not
  participate in band-merging (4-gate min for v0). Once
  substrate exists, gate is BINDING (5-gate min) — transition
  itself is ADR-gated.
- Correct decision-proxy-evidence schema field references:
  pinned_by/pinned_reason/second-reviewer → requested_by /
  proxied_by / review.peer_reviewer per actual
  docs/decision-proxy-evidence/_template.yaml.
- Cross-ref DRIFT-TAXONOMY pattern 5 to existing precursor doc
  docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md
  (referenced doc not yet present at top-level path).
- Reflow attribution scope para to remove line-leading `+`
  (markdownlint MD032 / Copilot finding).
- BACKLOG: extend Otto-52 name-attribution policy row with Otto-279
  reinforcement — research/** is HISTORY surface, first-name
  attribution applies to humans AND agents; post-drain sweep
  scope to restore stripped names on PR #351 and audit other
  research-doc PRs from the literal-rule window.

Per Aaron's clarification on this round: research docs ARE history,
so name-attribution policy ALLOWS first-name references for both
human contributors and agent personas. Reverted name-stripping
edits made earlier in this thread mid-tick when policy was
re-clarified. Memory: feedback_research_counts_as_history_*.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* drain: clear remaining markdownlint failures on #282

Four issues from gate run 24919099963:

- MD018 line 18: `#280); Otto-99 synthesis.` at line-start parsed as
  heading. Reflow to put `(PR #280)` together on prior line.
- MD018 line 140: `#266): \`band(...` same issue. Reflow.
- MD056 line 135: bare `|` characters inside table-cell inline-code
  (`|cone(q) ∩ cone(y)| / |cone(y)|`) parsed as column separators
  even though they're inside backticks. Replace with `size(...)`
  function syntax to remove the pipes — cleaner anyway.
- MD032 line 502: list missing blank line above bold-paragraph
  separator. Insert blank line.

No semantic change — gate-name fixes from earlier commit hold.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…C byte encoding

Two new Codex P1 findings on the BLAKE3 receipt-hashing v0 doc:

P1 (line 226) — replay determinism vs current signer set:
The req #4 said "compare commitment vs CURRENT signer-view",
which makes receipt validity time-dependent — the moment the
live signer set rotates, every prior receipt becomes invalid.
Replay-determinism breaks. Fix: validate against the signer
set authoritative at the receipt's claimed `policy_version`
(recoverable from `policy_version` + dispute-process
commitment-opening). Receipt-creation-time race-checking is
moved to the receipt-creation step; the replay gate catches
*forged* commitments only.

P1 (line 157) — canonical text-to-byte mapping:
The `len:u32-be ∥ bytes` framing for variable-length
identifiers (`budget_id`, `policy_version`, `node_id`)
specified the framing but not how to derive `bytes` from
the identifier string. Added explicit binding:
`bytes = NFC-normalised UTF-8 octets` — Unicode Normalization
Form C per Unicode Annex #15, then UTF-8 encoded. NFC fixes
visually-identical-but-byte-different forms (e.g., precomposed
vs decomposed accents); UTF-8 is the canonical text→byte map.
EOF

…C byte encoding

Two new Codex P1 findings on the BLAKE3 receipt-hashing v0 doc:

P1 (line 226) — replay determinism vs current signer set:
The req #4 said "compare commitment vs CURRENT signer-view",
which makes receipt validity time-dependent — the moment the
live signer set rotates, every prior receipt becomes invalid.
Replay-determinism breaks. Fix: validate against the signer
set authoritative at the receipt's claimed `policy_version`
(recoverable from `policy_version` + dispute-process
commitment-opening). Receipt-creation-time race-checking is
moved to the receipt-creation step; the replay gate catches
*forged* commitments only.

P1 (line 157) — canonical text-to-byte mapping:
The `len:u32-be ∥ bytes` framing for variable-length
identifiers (`budget_id`, `policy_version`, `node_id`)
specified the framing but not how to derive `bytes` from
the identifier string. Added explicit binding:
`bytes = NFC-normalised UTF-8 octets` — Unicode Normalization
Form C per Unicode Annex #15, then UTF-8 encoded. NFC fixes
visually-identical-but-byte-different forms (e.g., precomposed
vs decomposed accents); UTF-8 is the canonical text→byte map.
EOF

…th-ferry candidate #3) (#268)

* research: BLAKE3 receipt-hashing v0 design input to lucent-ksk ADR (7th-ferry candidate #3)

Responds to Amara's 7th-ferry BLAKE3 proposal (PR #259) +
Aminata's Otto-90 critiques (PR #263) flagging it belongs in
lucent-ksk rather than Zeta + naming side-channel-leakage and
cryptographic-agility gaps + Otto-91 addition of
parameter_file_sha binding for replay determinism.

v0 hash input set (8 fields, changes marked):

  h_r = BLAKE3(
    hash_version                    // NEW — crypto-agility
    ∥ h_inputs
    ∥ h_actions
    ∥ h_outputs
    ∥ budget_id
    ∥ policy_version
    ∥ parameter_file_sha            // NEW — Otto-91
    ∥ approval_set_commitment       // CHANGED — side-channel
    ∥ node_id
  )

Signature structure adds *_key_version to each signature tuple
for per-key-rotation without breaking historical receipts.

Addresses Aminata's 3 findings:
- Side-channel leakage: raw approval_set → Merkle/sorted-hash
  commitment; read-only observers see a hash, dispute process
  opens it.
- Cryptographic-agility: hash_version prefix + *_key_version
  binding; algorithm downgrade blocked because version is
  inside the hash.
- Approval-withdrawal race (top-3 #2): commitment mismatch at
  replay-time invalidates the receipt.

4 replay-deterministic harness requirements for Zeta-module
consumer side:
1. Same fields = same materialised views byte-for-byte.
2. Unknown hash_version = halt-and-report.
3. Unresolvable parameter_file_sha = halt-and-report.
4. Mismatched approval_set_commitment = reject receipt.

Explicit NOT-scope:
- Doesn't decide signature algorithm (Ed25519 is v0
  assumption, scheme accommodates later).
- Doesn't define hash_version / parameter_file registries
  (lucent-ksk governance artifacts).
- Doesn't define commitment scheme specifics (Merkle vs
  sorted-hash-list; affects dispute only).
- Doesn't implement rotation runbook.
- Doesn't include Bitcoin anchoring (separate trust-model).

7 dependencies to adoption in priority order; Aminata 2nd
pass first; cross-repo lucent-ksk ADR second; Max-specific
asks framed per Otto-90 specific-ask-channel calibration.

This is Zeta-SIDE design input. Canonical ADR belongs in
lucent-ksk per Aminata Otto-90 framing. No adoption until
cross-repo ADR lands.

Max attribution preserved first-name-only. Cross-repo work
on lucent-ksk does not touch Max's substrate directly until
actual coordination warrants — specific-ask channel is the
right escalation.

Archive-header format self-applied — 10th aurora/research
doc in a row.

Lands within-standing-authority per Otto-82/90 calibration.

Closes 7th-ferry absorb candidate #3 of 5. Remaining:
- #1 KSK-as-Zeta-module implementation (L)

Otto-92 tick primary deliverable.

* drain(#268 P2+P2+style+P1 Codex/Copilot): field count + version notation + canonical encoding

Four threads on the BLAKE3 receipt-hashing v0 design doc, all
on the same file.

P2 (lines 120 + 126): "8 fields" header / count text vs the
formula's 9 actual binding inputs (`hash_version` + 8 content
hashes). Reconciled to "9 fields" — the formula was the
source of truth, the count text was the lag.

Style (line 236): version notation inconsistency — `0x01` in
some places, `v0x02` / `v0x01` in others. Standardized on the
byte-literal hex notation `0x01` / `0x02` everywhere; the
"v" prefix doubled up with `hash_version =` already in the
formula and added no information.

P1 (line 132): hash binding used raw `∥` concatenation of
variable-length fields, opening a length-extension /
boundary-shift adversary surface. Added an explicit
`encode(·)` wrapper per field with a canonical-encoding
section: 1-byte version, 32-byte fixed-width digests for
content/policy/commitment hashes, and `len:u32-be ∥ bytes`
length-prefix framing for variable-length identifiers
(budget_id, policy_version, node_id). Forward-compatibility
preserved — future schemes (`hash_version >= 0x02`) can pick
different framing (CBOR / Protobuf / RFC 8949 §3.1 TLV) and
the version prefix tells verifiers which framing applies.

All 4 Codex/Copilot threads (PRRT_kwDOSF9kNM59SMrz,
PRRT_kwDOSF9kNM59SNsm, PRRT_kwDOSF9kNM59SNsy,
PRRT_kwDOSF9kNM59SNs2) addressed in this commit.

* drain(#268 lint): MD032 — line-leading + interpreted as list bullet (wrap fix)

* drain(#268 P1+P1 Codex): replay-determinism on signer view + UTF-8/NFC byte encoding

Two new Codex P1 findings on the BLAKE3 receipt-hashing v0 doc:

P1 (line 226) — replay determinism vs current signer set:
The req #4 said "compare commitment vs CURRENT signer-view",
which makes receipt validity time-dependent — the moment the
live signer set rotates, every prior receipt becomes invalid.
Replay-determinism breaks. Fix: validate against the signer
set authoritative at the receipt's claimed `policy_version`
(recoverable from `policy_version` + dispute-process
commitment-opening). Receipt-creation-time race-checking is
moved to the receipt-creation step; the replay gate catches
*forged* commitments only.

P1 (line 157) — canonical text-to-byte mapping:
The `len:u32-be ∥ bytes` framing for variable-length
identifiers (`budget_id`, `policy_version`, `node_id`)
specified the framing but not how to derive `bytes` from
the identifier string. Added explicit binding:
`bytes = NFC-normalised UTF-8 octets` — Unicode Normalization
Form C per Unicode Annex #15, then UTF-8 encoded. NFC fixes
visually-identical-but-byte-different forms (e.g., precomposed
vs decomposed accents); UTF-8 is the canonical text→byte map.
EOF

* drain(#268 P1+P2 Codex): correct adversary terminology + decouple CBOR/TLV citations

P1 (line 144) — terminology correction:
"length-extension / boundary-shift adversary surface"
incorrectly conflated two distinct attacks. BLAKE3 is built
on a tree-hash construction with finalisation flags — it is
NOT vulnerable to length-extension the way SHA-256 and MD5
are. The actual risk in raw concatenation is boundary-shift
/ collision-by-reframing only. Updated the wording to name
that risk explicitly and added a parenthetical noting that
length-extension is NOT a concern with BLAKE3.

P2 (line 162) — CBOR vs TLV reference correction:
'domain-separated TLV per RFC 8949 §3.1' conflated two
distinct concepts: RFC 8949 is CBOR (tagged data items), and
'domain-separated TLV' is a separate framing concept. Split
into two parallel options: 'CBOR per RFC 8949' (one option)
and 'a domain-separated TLV scheme' (another, no specific RFC
attached because TLV is generic). Future ADR can pick either
or define a custom TLV; the v0 doc no longer mis-cites.

* drain(#268 P1×3 Codex): version-policy gate + retired-key restriction + signed key-version

Three substantive Codex P1 findings on the v0 receipt-hashing design:

P1 (line 229) — version policy gate beyond unknown:
Req #2 only fail-closed on unknown hash_version. Updated to
also reject DEPRECATED versions per a policy registry
(lucent-ksk governance artifact). Prevents forgery under an
old-but-still-mechanically-recognised version that was
retired due to weakness. Historical receipts remain
verifiable for audit; new receipts under deprecated versions
are refused.

P1 (line 211) — retired key versions:
Rotation introduced agent_key_version/node_key_version but
didn't restrict NEW receipts from using retired key versions.
Added: separate registry of retired key versions blocks
creation of new receipts under retired versions; historical
receipts under retired versions remain verifiable
(replay-determinism preserved) but the signing path refuses
to produce more.

P1 (line 203) — signed key-version (authenticated metadata):
The notation `Sign_{sk, *_key_version}(h_r)` was ambiguous
about whether *_key_version was authenticated. If it's
unsigned metadata, an attacker can swap the declared version
to one that points at a public key for a different signature
algorithm. Fix: bind the version INSIDE the signed message
(`Sign_{sk}(version ∥ h_r)`) and verify by recomputing the
signing input from the declared version. Verification block
added showing the explicit lookup + recompute pattern.

Also reframed line 120 to make the field-count reasoning
explicit (Amara's 7 base + hash_version + parameter_file_sha
= 9 v0 fields) so the count claim isn't load-bearing on the
preceding paragraph alone.

* drain(#268 P1+P1 Codex): u32-be encoding for key-version + issuance-epoch gate on deprecated hash_version

Two more substantive Codex P1 findings:

P1 (line 208) — canonical encoding for key-version:
The signature scheme bound *_key_version into the signed
message but didn't specify the byte encoding. Added explicit
`encode_u32_be` wrapper + an Encoding section: 4-byte
big-endian unsigned integer, monotonic from 1, with version 0
reserved for uninitialised. Fixed-width avoids needing a
length prefix (every version is exactly 4 bytes).

P1 (line 260) — issuance-epoch gate on deprecation:
Unconditionally rejecting receipts with deprecated
hash_version breaks audit/replay of historical receipts that
were valid when issued. Updated to issuance-epoch gate:
receipts issued BEFORE the version's deprecation cutoff
remain valid for audit; receipts claiming an issuance epoch
AFTER the cutoff under that version are rejected. Registry
stores (version, deprecated_after_epoch) tuples; verifier
compares claimed issuance epoch against deprecation epoch
for that version.

Codex P2: the changes-from-Amara list at line 199 enumerated
'1. hash_version, 2. parameter_file_sha, 3. approval_set →
commitment' but didn't include the issuance_epoch addition.
Added as #3, renumbered approval_set replacement to #4. Now
the changes-list matches the v0 hash-input definition (10
fields = 7 base with approval_set→commitment swap + 3 v0
additions: hash_version + parameter_file_sha + issuance_epoch).

… + parameter_file_sha algo (#431)

* drain(#268 follow-up): add issuance_epoch field + clarify Amara attribution + parameter_file_sha algo

Three substantive Codex post-merge findings on PR #268:

P0 (line 275) — issuance_epoch bound into h_r:
The earlier issuance-epoch deprecation gate referred to a
'claimed issuance epoch' that wasn't actually defined as a
receipt field. Without binding it into h_r, an attacker could
forge a receipt under a deprecated hash_version and put the
claimed epoch BEFORE the deprecation cutoff to slip past the
gate. Fix: add issuance_epoch as a 10th hash-input field
(u64-be milliseconds since Unix epoch), bound into h_r.
Field count v0: 10 (was 9). Hash input set diagram updated.

P1 (line 126) — Amara attribution accuracy:
Earlier line said Amara's 7th-ferry proposal had
approval_set_commitment, but the original was approval_set
(raw) — Aminata's side-channel finding is what motivated the
v0 swap to approval_set_commitment. Updated attribution to
say 'approval_set [raw, replaced by approval_set_commitment
in v0 per Aminata's side-channel finding — same slot,
different binding]'.

P1 (line 166) — parameter_file_sha name vs BLAKE3 algorithm:
Field name implies SHA-family but the canonical encoding
specifies BLAKE3-256. Added clarification: the '_sha' suffix
is legacy Otto-91 naming (where '_sha' meant 'hash digest'
in that context); the actual algorithm bound by hash_version
= 0x01 is BLAKE3-256. Future schemes may pick different
digest algorithms via the hash_version registry; the field
name stays for Otto-91-prose compatibility.

* drain(#431 P2 Codex): add issuance_epoch entry to changes-list

Codex P2: the changes-from-Amara list at line 199 enumerated
'1. hash_version, 2. parameter_file_sha, 3. approval_set →
commitment' but didn't include the issuance_epoch addition.
Added as #3, renumbered approval_set replacement to #4. Now
the changes-list matches the v0 hash-input definition (10
fields = 7 base with approval_set→commitment swap + 3 v0
additions: hash_version + parameter_file_sha + issuance_epoch).

* drain(#431 P1+P1 Codex): forward-pointer for parameter_file_sha + backdating limitation note

Two substantive Codex post-merge findings on PR #431:

P1 (line 183) — forward-pointer for parameter_file_sha:
The field name implies SHA-256 binding via the early Otto-91
quote; the legacy-naming clarification appears later in the
canonical-encoding section. Readers may miss it. Added an
inline parenthetical at the field's first introduction
(line 126-130 area) noting the legacy-naming + actual-algorithm
distinction, with a 'details below' pointer.

P1 (line 130) — backdating limitation:
Binding issuance_epoch into h_r prevents POST-signature
mutation only — it does NOT prevent a compromised signer or
coerced agent from setting issuance_epoch BEFORE the
deprecation cutoff at receipt-creation time. Added an
explicit 'Backdating limitation' section listing three
mitigations (RFC 3161 TSA / Aurora-anchored chained
timestamps / forward-only highest-epoch registry), with v0
explicitly documenting the gap as known and deferring the
specific countermeasure to the lucent-ksk ADR.

…spine research doc (8th-ferry candidate #2)

M-effort technical spine per Amara 8th-ferry landing plan
(PR #274). Defines the 4-layer substrate (canonicalisation
+ representation + retrieval + scoring-sketch) that the
provenance-aware bullshit detector (candidate #3) and
operational EVIDENCE-AND-AGREEMENT (candidate #4) build on.

Four-layer structure:

**Layer 1 — Canonicalisation N(x)** with 4 required
properties (idempotent / deterministic / meaning-preserving
/ version-pinned). Input-type archetypes (natural-language
/ structured / code-diffs) named as downstream design
choices, not committed.

**Layer 2 — Representation φ(c)** — dense embeddings OR
binary semantic hashes (Hinton & Salakhutdinov) OR both.
Locality-sensitive hashing (Charikar) as complement for
cheap candidate retrieval. Product quantization for
corpus-scale compression when warranted.

**Layer 3 — ANN retrieval** — HNSW (Malkov-Yashunin 2018)
as default with substitutable-interface spine. Retraction-
native integration: RetrievalIndex IS a Zeta-module
materialised view over event stream (insert/remove);
`remove` is a negative-weight event not a tombstone. Same
pattern as KSK-as-Zeta-module budgets / receipts.
Replay-determinism at query-behaviour layer.

**Layer 4 — Scoring (sketch only)** — Amara's formulation
preserved:
  score(y|q) = α·sim + β·evidence - γ·carrierOverlap
             - δ·contradiction
Four terms map to: representation+kNN / citations-as-first-
class / provenance-graph / retraction-ledger. Full
formalisation is candidate #3.

Aminata-concern preview (previewed from oracle-scoring-v0
Otto-90 pass): gameable-by-self-attestation (evidence and
contradiction must come from independent oracles); parameter-
fitting adversary (ADR gate on α/β/γ/δ); false-precision
(band output not decimal).

PatternLedger schema (retraction-native):
- Events: PatternInserted / PatternRetracted / PatternSuperseded
  / ProvenanceEdgeAdded / ProvenanceEdgeRemoved
- Views: CurrentKnownGood / CurrentKnownBad / ContradictingPairs
  / ProvenanceCone

Composition-table shows spine slots into existing substrate
without new mechanisms: SD-9 (norm→mechanism); DRIFT pattern
5 (diagnostic→engine); citations-as-first-class (graph→
consumer); alignment-observability (anti-gaming discipline);
oracle-scoring v0 (band output pattern); BLAKE3 v0
(parameter_file_sha binding extends to N-version+φ-version);
quantum-sensing analogies #2+#4 (correlation and decoherence
slot into layers 3 and 4); KSK-as-Zeta-module 7th ferry
(same event+view module pattern).

Scope limits (6 items): no specific embedding-model commit;
no HNSW-exclusive commit; no canonicalisation-specifics
commit; no full scoring formalisation (that's #3); no
implementation proposal; does not replace citations-as-first-
class.

9 dependencies-to-adoption in priority order: Aminata pass at
#1; candidate #3 scoring formalisation at #2; candidate #4
operational promotion at #3; parameter choices / library
choices / property tests / ADR-gate substrate at downstream
positions.

Archive-header format self-applied — 15th aurora/research
doc in a row.

Lands within-standing-authority per Otto-82/90/93
calibration — research-grade substrate synthesis; not
implementation; not adoption; not gated.

Closes 8th-ferry candidate #2 of 3 remaining (after Otto-96
TECH-RADAR + Otto-97 quantum-sensing). Remaining:
- #3 Provenance-aware bullshit-detector (M; composes on top)
- #4 EVIDENCE-AND-AGREEMENT future operational (gated on #3)

Otto-98 tick primary deliverable.

…spine research doc (8th-ferry candidate #2)

M-effort technical spine per Amara 8th-ferry landing plan
(PR #274). Defines the 4-layer substrate (canonicalisation
+ representation + retrieval + scoring-sketch) that the
provenance-aware bullshit detector (candidate #3) and
operational EVIDENCE-AND-AGREEMENT (candidate #4) build on.

Four-layer structure:

**Layer 1 — Canonicalisation N(x)** with 4 required
properties (idempotent / deterministic / meaning-preserving
/ version-pinned). Input-type archetypes (natural-language
/ structured / code-diffs) named as downstream design
choices, not committed.

**Layer 2 — Representation φ(c)** — dense embeddings OR
binary semantic hashes (Hinton & Salakhutdinov) OR both.
Locality-sensitive hashing (Charikar) as complement for
cheap candidate retrieval. Product quantization for
corpus-scale compression when warranted.

**Layer 3 — ANN retrieval** — HNSW (Malkov-Yashunin 2018)
as default with substitutable-interface spine. Retraction-
native integration: RetrievalIndex IS a Zeta-module
materialised view over event stream (insert/remove);
`remove` is a negative-weight event not a tombstone. Same
pattern as KSK-as-Zeta-module budgets / receipts.
Replay-determinism at query-behaviour layer.

**Layer 4 — Scoring (sketch only)** — Amara's formulation
preserved:
  score(y|q) = α·sim + β·evidence - γ·carrierOverlap
             - δ·contradiction
Four terms map to: representation+kNN / citations-as-first-
class / provenance-graph / retraction-ledger. Full
formalisation is candidate #3.

Aminata-concern preview (previewed from oracle-scoring-v0
Otto-90 pass): gameable-by-self-attestation (evidence and
contradiction must come from independent oracles); parameter-
fitting adversary (ADR gate on α/β/γ/δ); false-precision
(band output not decimal).

PatternLedger schema (retraction-native):
- Events: PatternInserted / PatternRetracted / PatternSuperseded
  / ProvenanceEdgeAdded / ProvenanceEdgeRemoved
- Views: CurrentKnownGood / CurrentKnownBad / ContradictingPairs
  / ProvenanceCone

Composition-table shows spine slots into existing substrate
without new mechanisms: SD-9 (norm→mechanism); DRIFT pattern
5 (diagnostic→engine); citations-as-first-class (graph→
consumer); alignment-observability (anti-gaming discipline);
oracle-scoring v0 (band output pattern); BLAKE3 v0
(parameter_file_sha binding extends to N-version+φ-version);
quantum-sensing analogies #2+#4 (correlation and decoherence
slot into layers 3 and 4); KSK-as-Zeta-module 7th ferry
(same event+view module pattern).

Scope limits (6 items): no specific embedding-model commit;
no HNSW-exclusive commit; no canonicalisation-specifics
commit; no full scoring formalisation (that's #3); no
implementation proposal; does not replace citations-as-first-
class.

9 dependencies-to-adoption in priority order: Aminata pass at
#1; candidate #3 scoring formalisation at #2; candidate #4
operational promotion at #3; parameter choices / library
choices / property tests / ADR-gate substrate at downstream
positions.

Archive-header format self-applied — 15th aurora/research
doc in a row.

Lands within-standing-authority per Otto-82/90/93
calibration — research-grade substrate synthesis; not
implementation; not adoption; not gated.

Closes 8th-ferry candidate #2 of 3 remaining (after Otto-96
TECH-RADAR + Otto-97 quantum-sensing). Remaining:
- #3 Provenance-aware bullshit-detector (M; composes on top)
- #4 EVIDENCE-AND-AGREEMENT future operational (gated on #3)

Otto-98 tick primary deliverable.

…N LANDED)

Creates docs/bootstrap/ directory with three skeletons:

- README.md — directory overview + reviewer roster +
  why-both-anchors + cadence for content population
- quantum-anchor.md — algebraic substrate skeleton; 8
  section scaffolds with "placeholder — reviewer X to
  substantiate" markers
- ethical-anchor.md — ethos substrate skeleton; 8
  section scaffolds (Universal welcome first; tradition-
  neutral properties; christ-consciousness as Aaron's
  vocabulary; multi-tradition grounding paths; corporate-
  religion joke exegesis; composition; for-AI-agents
  substrate-ingestion; what-NOT)

All three absorb directives from:
- project_quantum_christ_consciousness_bootstrap_hypothesis
  (safety properties substantiated by these docs)
- project_common_sense_2_point_0 (5-property + candidate
  6th)
- feedback_christ_consciousness_is_aarons_ethical_vocabulary
  (universal welcome framing)
- project_craft_secret_purpose (yin/yang mutual alignment
  + Craft companion curriculum)

Reviewer roster: Aminata / Nazar / Kenji / Kira / Iris /
Rune / eventually Amara. 10-20 tick content-population
cycle estimated.

Gap #4 status: pending → SKELETON LANDED. Full content
population is reviewer-dependent L follow-on.

Attribution: Otto (loop-agent PM hat) skeleton; named
reviewers own content population.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>